Concept Testing Questions: What to Ask Reviewers
The questions you ask in a concept test decide how useful the results are. Vague prompts like "what do you think?" produce opinions. Focused questions produce a signal you can act on.
This is the question set Teststrip uses inside guided decision rooms for packaging, naming, product concepts, campaign directions, and creative reviews.
Ask about the concept, not the execution
Early concepts are unfinished on purpose. If you ask reviewers to react to a rough comp, you will get notes about the font and the photo crop instead of the idea.
Frame every question around the idea being tested, and say plainly which details are not final. Reviewers follow the frame you give them.
- What is this product or idea, in your own words?
- Who does this seem to be made for?
- What is the main promise this concept is making?
- What feels unclear or missing?
Comparison questions beat rating scales
A 1-to-5 rating on a single concept tells you almost nothing, because reviewers have no reference point. Showing routes side by side and asking for a choice produces a much cleaner signal.
Ask reviewers to review every route first, then commit to one and explain the reasoning. The explanation is the part your team will actually use later.
- After reviewing all the routes, which one would you pick and why?
- What made the other routes weaker for you?
- Which route would you be most likely to buy or recommend?
- Is there anything from another route you would carry into the winner?
Purchase-intent and relevance questions
These questions test whether the concept connects to a real need. Keep them short and concrete - hypothetical spending questions tend to be unreliable, but relevance questions hold up well.
- How well does this fit a problem you actually have?
- When would you use this, and how often?
- What would you compare this to today?
- What would have to be true for you to choose this?
Diagnostic questions for the winning route
Once a direction is leading, switch from choosing to sharpening. These questions tell your team what to fix before the next round of work.
- What is the strongest part of this direction?
- What is the weakest part?
- What would make this clearer at a glance?
- What concerns or risks would you flag before this ships?
Questions to avoid
Some questions reliably damage a concept test. Leading questions push reviewers toward the answer you want. Stacked questions bury two ideas in one prompt. Design-critique questions invite reviewers to redesign the work instead of judging the idea.
- "Don't you think this one is stronger?" - leading
- "Is this clear and appealing?" - two questions in one
- "What would you change about the layout?" - invites redesign
- "Would you buy this for $40?" - anchors on a price you have not tested
How many questions is right
Four to seven questions per concept test is the practical range. Fewer and you cannot separate a preference from its reason; more and completion rates fall and answers get shorter.
In a Teststrip decision room, reviewers see the routes together, pick one, and answer a short set of focused questions about their pick. Responses are grouped into themes so you can see what is leading and why without reading every comment individually.
Common questions
How many reviewers do I need for a concept test?
For internal creative decisions, 8 to 15 focused reviewers is usually enough to see a clear pattern. Qualitative concept testing is about reading direction and reasoning, not statistical significance.
Should reviewers see all concepts at once?
Yes for direction-setting work. Side-by-side comparison gives reviewers a reference point and produces sharper reasoning than rating one concept in isolation.
Should concept testing questions be open-ended or multiple choice?
Use a forced choice for the pick itself, then open-ended questions for the reasoning. The choice gives you a countable signal; the open text gives you the rationale to document.
What do I do with the answers?
Group them into themes, note which route led and why, record the concerns raised, and write down what was rejected. That record is what keeps the decision from being relitigated later.
Run your next creative decision in a room built for it.
Upload the routes, invite reviewers with one link, read the signal, and leave with a documented decision record.