# Concept Testing

Concept testing evaluates whether a proposed product direction is understandable, relevant, credible, and differentiated before a team commits to detailed design or delivery.

- Type: method
- Domain: Experience & interface
- Level: Advanced
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/concept-testing/>)

## What it means

Concept testing presents a deliberately incomplete expression of an idea—such as a proposition, storyboard, service scenario, or rough prototype—to people from the intended audience. It investigates how they interpret the concept, which needs it appears to address, and what concerns or expectations it creates. It tests the direction, not the usability of a finished interface.

## Why it matters

Teams can build a polished solution to a weak proposition. Concept testing exposes mismatches in problem relevance, language, trust, perceived value, and differentiation while alternatives are still inexpensive to change. It also produces better questions for later discovery instead of reducing an uncertain idea to a single approval score.

## When to use it

Use it in discovery or an alpha phase when several solution directions could address a validated problem, or when a new proposition carries substantial desirability or comprehension risk. It is less useful when the concept is too vague to interpret or when the real uncertainty is task performance in a detailed workflow.

## How it works

1. Define the learning questions and recruit participants who face the relevant situation or decision.
2. Create comparable concept stimuli with enough context to understand the promise but not enough polish to imply completion.
3. Ask participants to explain the idea in their own words before probing appeal, relevance, credibility, alternatives, and concerns.
4. Compare patterns across concepts and audience segments; separate comprehension problems from genuine lack of value.
5. Revise or retire concepts, then test risky interactions, feasibility, and behavior with appropriate follow-up methods.

## A practical example

A small-business banking team compares three ways to help owners manage irregular cash flow: automatic reserves, predictive warnings, and a flexible credit buffer. Interviews reveal that warnings are understood but feel passive, while automatic reserves raise control concerns. The team combines forecasted warnings with an optional rule-based reserve and prototypes the setup flow for usability testing.

## Where it breaks

Stated interest is not purchase, adoption, or sustained behavior. Results are highly sensitive to recruitment, framing, concept detail, price context, and the alternatives shown. Participants may praise an idea to be agreeable or reject it because essential operational details are absent. Concept testing should narrow uncertainty, not manufacture a forecast.

## Common mistakes

- Asking whether participants like an idea instead of examining interpretation, relevance, tradeoffs, and current alternatives.
- Showing one polished concept and treating reactions as comparative evidence.
- Using concept feedback to claim that a workflow is usable or that market demand is proven.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/concept-testing/#visualization-concept-testing>)

## Sources

1. [How the Alpha Phase Works](<https://www.gov.uk/service-manual/agile-delivery/how-the-alpha-phase-works>) — Government Digital Service · Government guidance
2. [User Research in Alpha](<https://www.gov.uk/service-manual/user-research/user-research-in-alpha>) — Government Digital Service · Government guidance
3. [UX Research Methods: Glossary](<https://www.nngroup.com/articles/research-methods-glossary/>) — Nielsen Norman Group · Professional guidance

## Related topics

- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
- [Prototype Fidelity](<https://wiki.soroush.uk/topic/prototype-fidelity/>)
- [Usability Testing](<https://wiki.soroush.uk/topic/usability-testing/>)
