Concept Test

Purpose

Concept Testing puts a design concept in front of real users to gauge whether it resonates — before building it. It answers three questions: Do users understand it? Do they want it? Would they switch from their current solution? The feedback directs the team to refine, pivot, or proceed with confidence.

At a glance

• Group size: 1 facilitator + 1 user per session (run 5–8 sessions)
• Duration: 40 minutes per session
• Difficulty: Moderate
• Facilitation style: Semi-structured interview around a concept stimulus
• Setting: Quiet room or video call

How to run

1. Prepare the concept stimulus (beforehand): Create a concept poster, prototype, storyboard, or landing page that communicates the idea without jargon.
2. Introduce without selling (5 min): Show the concept. Ask the user to describe what they see in their own words. Do not explain or pitch.
3. Assess comprehension (10 min): "What do you think this does?" "Who is this for?" "What would you use it for?" Note misunderstandings.
4. Assess desirability (10 min): "How would this fit into your life/work?" "What excites you?" "What concerns you?" "What’s missing?"
5. Assess adoption intent (10 min): "Would you use this?" "Would you pay for it?" "What would you stop using?" "What would have to be true?"
6. Debrief (5 min): Summarise what you heard. Note the user’s emotional tone, not just their words.

Materials needed

• Concept stimulus (poster, prototype, mockup, or landing page)
• Interview guide with questions for each assessment area
• Recording device (with consent)
• Observation template

Pitfalls & common mistakes

• Selling the concept: If you explain why it’s great, you’ll get polite agreement, not honest feedback.
• Asking "Do you like it?": Too vague. Ask specific, behavioural questions.
• Testing with colleagues: They know too much context. Test with real target users.
• One test = decision: Run at least 5 sessions before drawing conclusions.

Inclusion & accessibility

• Provide the concept stimulus in accessible formats (large print, screen-reader compatible).
• Allow users to respond in their preferred language.
• Test with users who represent the diversity of the target population.

Variations

• A/B concept test: Show two concepts and ask users to compare and choose.
• Fake door test: Create a landing page for the concept and measure sign-up rates.
• Concept walkthrough: Walk the user through the concept step by step like a guided prototype.

When NOT to use this

• When the concept is too abstract for users to evaluate — make it more tangible first.
• When you need quantitative validation — use surveys or A/B tests with larger samples.
• When the concept is confidential and sharing it would create competitive risk.

Source & further reading

• Ulwick, Anthony — *What Customers Want* (McGraw-Hill, 2005)
• Cagan, Marty — *Inspired: How to Create Tech Products Customers Love* (Wiley, 2017)
• IDEO — *The Field Guide to Human-Centered Design* (2015)