Concept Testing

Early testing of concepts (wireframes, narratives, prototypes) with target users to evaluate appeal, clarity, and fit before investing in development.

Process

Key Fields

Question it answers	Do users understand the concept? Does it address their need? Would they be willing to try it?
Participants & timing	8-15 users per concept · 20-30 min per test · 2-3 weeks
AI compatibility	AI transcribes feedback and clusters reactions by theme; interpretation of appeal vs. skepticism requires human judgment.
Output	Concept feedback summary (pros/cons), participant reactions highlight, refined concept recommendations, go/no-go decision support

Use when

Multiple concept directions are competing and need prioritization
Validation is needed before expensive development begins
Ideas are being tested with actual users for the first time
Concept success metrics are unclear

Skip when

Concept is already heavily developed and major changes are off the table
Solution direction is locked by business or technical constraints

Common Mistakes

Leading questions

"Don't you love this idea?" vs. "What's your reaction?" Neutral open prompts capture honest feedback. Silence after the question is acceptable; don't fill it by restating the concept.

Testing the wrong user segment

Testing a B2B SaaS concept with casual users produces irrelevant feedback. Match test participants to the actual target user type.

Over-investing in artifact realism

Concept test fidelity matters less than idea clarity. A detailed wireframe and a crude sketch often generate the same feedback; the wireframe takes ten times longer to create.