Guide
How to test a prototype with users
To test a prototype, decide what you need to learn, find about five people who match your target customer, give them realistic tasks, and watch or ask what happened without explaining the product. Look for patterns, not single opinions. Remotely, run live interviews on a call or send a link with a short form. AppSprint's Full and Focused sprints include an editable feedback form that testers open without an account; its results do not establish product-market fit.
What a prototype test is for
A prototype test answers narrow questions early: do people understand this, can they complete the main task, do they care? In the book Sprint by Jake Knapp, John Zeratsky and Braden Kowitz, the last day of the sprint is five one-on-one customer interviews. The number follows Jakob Nielsen's usability research: after a handful of testers the main problems start repeating.
A test of this size finds problems and signs of interest. It does not measure demand, predict sales or prove product-market fit, whatever the answers are.
Run the test step by step
Write down what you need to learn (15 minutes)
List two or three questions the team is betting on. Every task should serve one of them.
Find about five testers (start a week ahead)
Recruit people who match the target customer, not colleagues or friends.
Prepare tasks and questions (30 minutes)
Write realistic tasks ("you want to book a repair for tomorrow") and open questions. Avoid asking whether they like it or would buy it.
Run each session (30 to 60 minutes live, about 5 by form)
Live: ask about the person, hand over the prototype, ask them to think aloud, then stay quiet. Do not explain or defend. By form: send the prototype link and the questions and let people answer in their own time.
Look for patterns (1 hour)
Put the notes side by side. A problem most testers hit is real. A comment one person made is a lead, not a finding.
Decide what changes
Turn the patterns into a short list of actions with owners.
Common mistakes
- Pitching before the tester has tried anything. You are then testing your pitch.
- Leading questions such as "Was that easy?" Ask "What happened there?"
- Counting compliments. People are polite about prototypes; watch what they do.
Testing remotely: live interview or feedback form?
| Live interview on a call | Link and feedback form | |
|---|---|---|
| What you learn | Where people hesitate and why | Written reactions and ratings from more people |
| Effort | Scheduling, an interviewer, a note taker | Send a link and wait |
| Main risk | The interviewer leads the tester | Short answers, no chance to ask why |
| Best for | Confusing flows and new concepts | A first read of interest and obvious problems |
Doing this in AppSprint
The Full Product Sprint and Focused Product Sprint include three testing steps: Create Feedback Form, Invite Testers and Review Feedback. This is the form route, not live interviews. Each prototype has its own public form that needs no account. The tester sees a button that opens the prototype in a new tab, then the questions. No name or email is collected, and responses appear as "Anonymous tester".
The default questions include "How disappointed would you be if you could no longer use this product?", an experience rating, what worked well and what could be improved. The team can edit the form, up to 20 questions. The team also co-edits one invitation email, but AppSprint does not send it or recruit testers: you copy the text or open it in your own mail app. See user testing feedback forms.
Responses arrive on a live dashboard with per-question breakdowns and a filter by prototype, and any answer can become an action item. There is no AI analysis. The dashboard states that the results do not establish product-market fit. The One-Hour Sprint has no testing steps.