Product review
A full product review: stars, NPS, a matrix across characteristics and a ranking of features by importance. Built for a recurring measurement, not a one-off website form.
Who it is for and when to run it
This survey is for a product team that wants to see how users rate the product piece by piece. Run it once a quarter or after a major release, and send it to active users who have formed an opinion.
It suits an app, a SaaS tool, an online course or a physical product with clear characteristics. Distribute it by email, as an in-app banner, or as a website widget for signed-in users.
If you want feedback from everyone, bugs and complaints included, the branching feedback form is a better fit. This template is built for a calm rating, not for someone reporting a problem.
What the template is made of
Every block in the order it sits in the builder. Branching decides which of them a given person actually sees.
- Your overall rating of the product Star rating
An overall star rating. It’s required and makes an easy opener that sets the context: we’re rating the product.
- Would you recommend the product? NPS (0–10)
NPS in the middle. Stars answer «how much do you like it»; NPS answers «would you put your reputation on it». The two often disagree, and the gap is more interesting than either number.
- Rate individual characteristics Matrix
A matrix across five qualities: interface, speed, design, stability, documentation. A 1 to 5 scale per row shows the weak spot without separate questions.
- Put the features in order of importance to you Ranking
Drag-and-drop feature ranking. People can’t say «everything matters», they have to choose an order, which shows what actually keeps them.
- What are you missing? Long answer
The open question «What are you missing?». Feature requests the team never listed above tend to show up here.
How to adapt the template
-
Replace the matrix rows with your product’s own qualities. A course might use «How material is explained», «Practice», «Tutor feedback».
-
Keep the ranking to five to seven items. With ten, people stop thinking and leave the default order.
-
If you need a split by user type, add a dropdown at the start: «How long have you used the product?».
-
Make the NPS question required if you plan to calculate the index; right now only the star rating is required.
How to read the results
Compare stars and NPS for the same people. High stars with low willingness to recommend usually mean the product is liked but hard to explain to others, or it only suits a narrow group.
In the matrix, look for the row with the lowest average and the widest spread. A low average with agreement means «bad for everyone». A wide spread means the quality works for some use cases and not others, so check who gives the low scores.
For the ranking, look at how often a feature comes first, not just its average rank. A feature that’s first for a third of users and last for the rest is holding a distinct segment.
Tag the «What are you missing?» answers by theme and compare them with your roadmap. A repeated request that isn’t planned deserves its own discussion.
Common mistakes
- Sending the survey to users on day one. They have nothing to rate yet and fill in the matrix at random.
- Growing the matrix to ten rows. People start giving the same number on every row just to finish.
- Treating the ranking as a vote on what to build. It shows what people value now, not what to make next.
Questions about the «Product review» template
What questions should a product feedback survey include?
An overall rating, likelihood to recommend, ratings for individual qualities, a feature priority ranking and an open question about what’s missing. That gives you a headline number for reports, an idea of what drives it, and a list of user ideas.
Why ask for both a star rating and NPS?
They measure different things. Stars show how much the person likes the product; NPS shows whether they’d recommend it to others. High stars with a low NPS mean people like it but don’t spread the word, which is worth investigating.
How often should you run a product feedback survey?
Once a quarter or after a major release. More often isn’t useful: product qualities change slowly, and frequent surveys wear out the same active users and lower your response rate.
Similar templates
-
Feedback form
A smart form with branching: the user picks a reason for getting in touch and gets their own set of questions.
-
NPS: loyalty index
The classic Net Promoter Score: one number, the reason behind it, and a contact.
-
CSAT: support ticket rating
A short pulse on support quality: a smiley, what worked and what did not.
Do not start from an empty canvas
Open the catalog, take the closest template and rewrite the questions for your job. Five minutes instead of an hour.