Prototype usability test questions
Questions for testing a clickable prototype before engineering starts — so you catch confusing flows and dead ends while they're cheap to fix.
Product designers and researchers validating a design — they spend their days in Figma turning ideas into flows, and needing to know a design works before handing it to engineering.
- What they're trying to learn
- validate that a proposed flow is understandable and completable before it's built.
- Who they interview
- target users representative of the real audience
Use this on clickable prototypes (Figma, etc.) before development. It's the cheapest point to fix a broken flow — pixels are far easier to change than shipped code.
Prototype testing questions to copy & run
Set expectations
- 1.This is an early prototype — some things are clickable and some aren't, and it's rough on purpose. Testing it helps us find problems early.
- 2.Before you start: what do you expect this to help you do?
Task walkthrough
- 1.Your goal is to [task]. Start whenever you're ready and think out loud.
- 2.What do you expect to happen when you tap that?
- 3.You seem unsure — what are you looking for?
- 4.If this were live, what would you do next?
- 5.(On a dead end) What did you expect to be here?
Reactions
- 1.How did that flow feel overall?
- 2.Was anything confusing or missing?
- 3.Did the steps happen in the order you expected?
- 4.What's the one thing you'd change before this ships?
Tips for better answers.
- Set expectations that it's rough and unfinished — it frees people to be critical.
- Test the flow and the mental model, not the pixels; visual polish comes later.
- When they hit a non-clickable dead end, ask what they expected there — that's a missing path.
- Keep tasks realistic and goal-based so you learn whether the concept works, not whether they can follow directions.
Questions about this template.
Can I run a usability test on a prototype?
Yes — testing a clickable prototype (in Figma or similar) is one of the highest-leverage things you can do. It validates a flow before engineering invests, when changes cost minutes instead of sprints.
How finished does a prototype need to be to test it?
Just enough to complete the target task — key screens and the main clickable path. Testing early, rough prototypes is a feature, not a limitation: unpolished designs invite more honest, critical feedback.
What's the difference between prototype testing and concept testing?
Concept testing gauges whether an idea resonates; prototype usability testing checks whether a specific interactive flow is understandable and completable. You concept-test to decide what to build and prototype-test to refine how it works before coding.
Don't just ask the questions — synthesize the answers.
Save these questions as a template in Intervool, capture the interview, and let AI turn every conversation into insights, personas, and a prioritized roadmap. Free for 30 days.