Product development survey templates
Decide what to build, and whether it worked. These templates cover the product lifecycle from idea screening and concept tests to beta feedback, usability and the question every product team should ask: how disappointed would you be without it?
- Concept & idea testing · 3
- Feature prioritisation · 3
- Beta & early access · 1
- Usability & UX · 2
- Packaging & design · 1
- In-app & website feedback · 3
13 of 13
Product development (13)
Concept & idea testing
- Concept testingUniqueness, relevance, believability, purchase intent and objections for a product concept shown as text or image.6 questions ~3 min
- Idea screeningRate up to six one-line ideas on appeal and need, then pick one, so you can shortlist before full concept tests.4 questions ~3 min
- Product-market fit surveyThe 'very disappointed' question plus who benefits most, the main benefit and what to improve, run quarterly.4 questions ~2 min
Feature prioritisation
- Feature prioritisationImportance and satisfaction for up to eight features, plus a forced ranking, to find the gaps worth closing.4 questions ~4 min
- Kano model surveyFunctional and dysfunctional pairs for each feature to classify must-haves, performance features and delighters.7 questions ~4 min
- Feature request formA structured way for users to ask for features: the problem, how they solve it today, impact and urgency.5 questions ~3 min
Beta & early access
Usability & UX
Packaging & design
In-app & website feedback
- Product feedbackFind out what people use, what frustrates them and what they would miss, so you can decide what to build next.7 questions ~4 min
- Website feedbackLearn why visitors came, whether they found it, and what got in the way.4 questions ~1 min
- Mobile app feedbackIn-app survey on ease of use, crashes, missing features and store rating intent, kept to five questions.5 questions ~2 min
Product development survey questions, answered
What is concept testing?
Showing a short description (and sometimes an image) of a product idea to target customers and measuring interest, uniqueness, believability, purchase intent and objections before building it.
What is a Kano survey?
A pair of questions per feature asking how the user would feel if it were present and if it were absent. The combination classifies features as must-have, performance, delighter or indifferent.
What should a beta feedback survey ask?
How often they used it, what they used it for, what did not work, how it compares to the old way, and whether they would keep it if it shipped as is.
What is a good System Usability Scale score?
The average across products is 68. Above 80 is excellent; below 50 indicates serious usability problems.
How do I test packaging designs?
Show two to four designs in random order, ask preference, clarity of what the product is, and perceived quality and price; then confirm with a forced choice.
How long should an in-app survey be?
One to three questions. The user is in the middle of something; ask the one thing you need and let them go.