Survey · Product
Product testing survey template
Anchored to the task you set: testers who finished easily move on, testers who struggled say which step was hardest, and testers who got stuck say where and can attach a screenshot. Everyone then says what they expected to happen, rates ease and quality, and reports any bugs they spotted.
Try it live
Try it as a respondent
Every question, and where it leads
The conversation
What a respondent is asked, in order.
Thanks for testing for us. Tell us what happened while it's fresh; the problems are the most useful part.
What's your name or tester ID?
What did you test it on?
Were you able to finish the task we gave you?
Which step was hardest, and why?
Where did you get stuck? Tell us what you were trying to do and what happened.
Got a screenshot or recording of the moment? Add it here.
What did you expect to happen instead?
Overall, how easy was it to use?
How would you rate the quality of what you tested?
Did you notice anything broken or behaving oddly?
What did you notice, and can you make it happen again?
Based on this test, would you use it for real?
If you could change one thing before launch, what would it be?
Ends with
Thanks for testing 🧪
The flow
Where each answer leads. Every route here is editable once the form is yours.
Short text
Dropdown
Single select
Long text
Long text
File upload
Long text
Opinion scale
Rating
Yes / No
Long text
Single select
Long text
What this template uses
- Short text
- Dropdown
- Single select
- Long text
- File upload
- Opinion scale
- Rating
- Yes / No
- 4 branches
Questions to consider
- What exact task will you give testers, and where will you describe it: in the invite or in the form?
- Which version or build are they testing, and should testers be asked to name it?
- Do you need screen recordings, or are screenshots enough to reproduce a problem?
- Who triages bug reports, and how quickly should testers hear back?
How to use the responses
Group the answers by task result first. Anyone who got stuck has shown you a blocker, so try to reproduce each one using their steps and screenshots. Then compare what testers expected with what happened: repeated mismatches point to a design problem rather than a bug. Keep bug reports and usability complaints in separate lists, since they usually go to different people.
How to customize and share it
- 1Describe the test task in the greeting or in the invite, and rename the device options to what you support.
- 2Add a question for the build or version number if you send the link for more than one release.
- 3Share the link with testers right after each session, and export the responses to CSV for your bug tracker.
Frequently asked questions
What questions should a product testing survey ask?
Whether the tester finished the task, where they struggled, what they expected instead, how easy and good it felt, any bugs they saw and whether they would use it for real.
Should every tester do the same task?
If you want to compare results, yes. Give free exploration its own round so you can tell which findings came from which kind of test.
How do I get useful bug reports from testers?
Ask what they were trying to do, what happened, whether they can make it happen again, and for a screenshot. This template asks all of these only of testers who hit a problem.
Can testers upload screenshots?
Yes. Testers who got stuck can attach images or short videos of the problem.