What it is
Presenting a concept, often as a description, sketch, or rough mockup, to users to assess whether it is understood, valued, and worth pursuing.
When to use it
Late Ideate into Prototype, when you have candidate concepts but have not committed to one.
Why (value)
Reduces the risk of building the wrong thing by testing desirability and comprehension while changes are still cheap.
How to run it
- Express each concept clearly and comparably.
- Recruit target users.
- Present concepts and ask about value, clarity, and fit.
- Probe what resonates and what confuses.
- Compare concepts and decide what to advance.
Inputs and outputs
- Inputs: One or more concepts, participants, a discussion guide.
- Outputs: Comprehension and desirability signals, a prioritized concept.
Time and effort
Medium. Light prep once concepts exist.
Evidence and limitations
Produces direct-user evidence about perceived value and understanding, not usability or real-world adoption; stated interest overpredicts actual behavior. See Evidence and limitations.
Tips and pitfalls
- Keep concepts at comparable fidelity.
- Separate “I understand it” from “I would use it.”
- Treat enthusiasm as a signal, not a commitment.
Variations
Single-concept, comparative, and monadic versus sequential presentation.
Related methods
Need help planning research or facilitating this method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- NN/g, “Concept Testing: Using Research to Shape Early Ideas.”
Explore related methods
- Desirability studies — Measure the emotional and aesthetic response a design evokes, not just whether it is usable.
- Usability testing — Watch representative users attempt real tasks to find where the design helps or gets in their way.
- Value proposition canvas — Map how a product's benefits fit the customer's jobs, pains, and gains.
