Concept testing

Concept testing evaluates customer response to a product idea before building it. Using descriptions, mockups, prototypes, or videos, teams present concepts to target users and gauge reactions - interest, understanding, concerns, and willingness to pay. This early-stage research helps validate that an idea is worth pursuing before significant development investment.

Why it matters

Building products is expensive. Even with agile methodologies, taking a concept from idea to shipped feature requires substantial time and resources. Concept testing matters because it reveals potential problems when changing course is cheap.

Concept testing answers fundamental questions:

Is this desirable? Do customers actually want this? Does it solve a problem they care about?

Is it understood? Do customers grasp what the concept is and what it offers?

Is it differentiated? Does it offer something meaningfully different from alternatives?

Is there willingness to pay? Would customers actually purchase this? At what price?

A concept that fails these tests likely fails in market, regardless of how well it's executed.

What to test

Concepts can be tested at various levels of fidelity:

Verbal descriptions. A written or spoken explanation of the product idea. Quick to create; may be too abstract for some concepts.

Concept boards. A visual presentation combining imagery, headlines, and descriptions that conveys the product idea and value proposition.

Mockups and wireframes. Visual representations of what the product might look like. More concrete than descriptions; still clearly unfinished.

Clickable prototypes. Interactive demonstrations that simulate key experiences. Enables testing reactions to actual interactions.

Video concepts. Videos that demonstrate the product in use, sometimes depicting features that don't exist yet.

Wizard of Oz testing. A working interface backed by human effort rather than real functionality. Tests the experience without building the technology.

Higher fidelity enables more realistic reactions but requires more investment. Match fidelity to what you need to learn.

Testing methods

Qualitative interviews. Present the concept and discuss reactions in depth. Understand why people respond as they do. Best for exploring reactions and uncovering concerns.

Surveys. Quantify reactions across a larger sample. Measure appeal, purchase intent, and preference against alternatives. Best for validating or comparing.

Focus groups. Discuss concepts with small groups. Group dynamics can surface reactions that individual interviews miss. Watch for groupthink.

Preference testing. Present multiple concepts and ask which users prefer and why. Useful when choosing between alternatives.

Fake door testing. Present the concept as if it exists (e.g., a button or landing page) and measure clicks or signups. Tests real behavior, not just stated intent.

Key metrics

Purchase intent. Would you buy this? How likely are you to purchase? The single most important indicator, though often overstated by respondents.

Relevance. Is this relevant to your needs? Do you experience the problem this solves?

Uniqueness. Is this different from what's available? Does it offer something you can't get elsewhere?

Believability. Do you believe this product can deliver what it promises?

Appeal. How appealing is this concept? Would you want to learn more?

Understanding. Do you understand what this product does? Confusion signals communication problems.

Testing best practices

Test with target customers. Reactions from non-targets mislead. Ensure your sample matches your intended market.

Describe the problem first. Validate that respondents experience the problem before showing the solution. If they don't have the problem, their solution feedback is less relevant.

Let respondents react, then probe. Get initial unguided reactions before asking specific questions. Probing too early can lead witnesses.

Watch for politeness bias. People tend to say nice things, especially face-to-face. Design questions and interpret responses accounting for this.

Test multiple concepts when possible. Comparative reactions are often more reliable than absolute ratings.

Pay attention to behavior, not just words. What people do (click, sign up, spend time) often differs from what they say.

Interpreting results

High intent is encouraging but not definitive. Stated purchase intent consistently overstates actual purchase behavior.

Confusion is a red flag. If customers don't understand the concept, execution won't save it.

Indifference is worse than dislike. Strong negative reactions at least indicate the concept provokes response. Indifference suggests irrelevance.

Specific concerns are valuable. When customers articulate why they're skeptical, you learn what must be addressed.

Segment differences matter. A concept that resonates with some segments and not others isn't failing - it's revealing its market.

Concept testing limitations

Doesn't replace market reality. Even strong concept testing can't guarantee market success. Execution, timing, and competition matter too.

Tests reactions to ideas, not products. Customers respond to what they imagine, which may differ from what you build.

Novelty is hard to test. Truly new concepts face customers who can't imagine what they haven't experienced.

Context is artificial. Testing environments differ from real purchase contexts.

Concept testing reduces risk but doesn't eliminate it. It's one input to decisions, not the decision itself.

When to test concepts

Early in development. Before significant investment, when pivoting is easy.

When considering multiple directions. Comparative testing helps choose between alternatives.

When uncertainty is high. Novel concepts or new markets carry more risk worth testing.

When stakeholders disagree. Customer data can resolve internal debates about concept merit.

Tools like Klero extend concept testing by connecting it to ongoing customer feedback. When concepts are informed by patterns in customer needs, testing validates whether proposed solutions resonate with those needs.