45 product feedback survey questions for every stage of the product
This bank contains 45 product feedback survey questions in seven sections: usage and habits, overall satisfaction, features, usability, product-market fit, pricing and value, and open-ended discovery. The most useful product surveys are short and targeted — 5–8 questions tied to one decision you're trying to make, like what to build next, why activation drops, or whether you've reached product-market fit.
How do you use this question bank?
Start from the decision, not the questions. If you're prioritizing the roadmap, use the feature and open-ended sections. If retention worries you, use satisfaction and product-market fit. If activation is the problem, use the usability section and target users in their first two weeks. A focused 5-question survey to the right segment beats a 30-question survey to everyone.
In-app micro-surveys (one or two questions at a relevant moment) get the highest response rates; email surveys work better for longer pulls like the product-market fit set. Mix question types: scales for tracking, multiple choice for facts, open text for discovery. If you need a free tool with unlimited responses for this, Formkii covers ratings, NPS, and branching logic out of the box.
| Goal | Sections to use | Best timing |
|---|---|---|
| Prioritize the roadmap | Features + open-ended | Quarterly, to active users |
| Diagnose churn risk | Satisfaction + product-market fit | Ongoing rolling sample |
| Fix onboarding | Usability | Day 7–14 after signup |
| Test pricing | Pricing and value | Before plan or pricing changes |
| Validate product-market fit | Product-market fit set | After users hit core value at least twice |
Usage and habits questions
- How often do you use [product]?
- What do you primarily use [product] for?
- Which task were you trying to complete the last time you used [product]?
- What did you use before [product], and what made you switch?
- Which other tools do you use alongside [product]?
- Who else on your team uses [product]?
- How long have you been using [product]?
Overall satisfaction questions
- Overall, how satisfied are you with [product]?
- How likely are you to recommend [product] to a friend or colleague? (0–10)
- How well does [product] meet your needs?
- What's the main reason for your satisfaction score?
- Compared to six months ago, is [product] getting better, worse, or staying the same?
- How does [product] compare to alternatives you've tried?
Feature questions
- Which feature of [product] do you use the most?
- Which feature could you not live without?
- Which features do you never use?
- Is there a feature you expected [product] to have but couldn't find?
- What's the one feature you'd add if you could?
- Of these planned features, which would help you most? (multiple choice from your roadmap candidates)
- Have you ever used a workaround or another tool because [product] couldn't do something? What was it?
- How satisfied are you with [specific new feature] released recently?
Usability questions
- How easy is [product] to use overall?
- How easy was it to get started the first time you used [product]?
- Was there a moment during setup where you got stuck or confused? What happened?
- How easy is it to find the features you need?
- How would you rate the speed and reliability of [product]?
- How clear are error messages and what to do when something goes wrong?
- If you had to teach a new teammate [product] in five minutes, what would be hardest to explain?
Product-market fit questions
The first question here is the well-known Sean Ellis test: if 40% or more of engaged users say "very disappointed", you're generally considered to have product-market fit signal.
- How would you feel if you could no longer use [product]? (very disappointed / somewhat disappointed / not disappointed)
- What type of person do you think would benefit most from [product]?
- What is the main benefit you get from [product]?
- How would you solve this problem if [product] didn't exist?
- What made you realize [product] was (or wasn't) right for you?
Pricing and value questions
- How would you rate the value for money of [product]?
- Does our pricing model (per seat, per usage, flat) make sense for how you use [product]?
- Which plan are you on, and does it fit your needs?
- What would justify a higher price for you?
- If budget were cut tomorrow, would [product] survive the cut? Why or why not?
Open-ended discovery questions
- If you could change one thing about [product], what would it be?
- What's the most frustrating part of using [product]?
- What's something [product] does better than anything else you've tried?
- What problem are you still solving with spreadsheets or manual work that you wish [product] handled?
- What almost stopped you from signing up?
- What would make [product] a 10 out of 10 for you?
- Anything else you want the product team to know?
Always pair "What feature should we add?" with "What problem would that solve for you?" Users are excellent at describing problems and unreliable at designing solutions — the second question is the one your product team can actually act on.
Tips for using these questions
- Segment before you send. Power users, new users, and churned users will give contradictory answers to the same question — and all three are right.
- Trigger surveys at relevant moments: after completing a key action, after a support ticket, on day 14, at renewal.
- Track 2–3 questions on a fixed cadence (satisfaction, NPS, the disappointment question) and rotate everything else.
- Count problem themes, not feature votes. Ten users asking for ten different features may all be describing the same underlying workflow gap.
- Cap in-app surveys at one or two questions; save anything longer for email with an honest time estimate.
- Close the loop in release notes: "you asked, we shipped" turns survey respondents into repeat respondents.
Frequently asked questions
What questions should a product feedback survey ask?
Anchor it to one decision. For roadmap prioritization, ask which features people use most, what's missing, and what problem a requested feature would solve. For retention, ask satisfaction, likelihood to recommend, and how disappointed they'd be if the product disappeared. Keep it to 5–8 questions per survey.
What is the product-market fit survey question?
The Sean Ellis question: "How would you feel if you could no longer use this product?" with options very disappointed, somewhat disappointed, and not disappointed. As a common rule of thumb, if at least 40% of engaged users answer "very disappointed", the product is showing product-market fit signal.
When should you send a product feedback survey?
Tie it to moments: 7–14 days after signup for onboarding feedback, immediately after using a new feature for feature feedback, quarterly for satisfaction tracking, and within days of cancellation for churn feedback. Moment-triggered surveys get better response rates and more accurate answers than random blasts.
How do you get users to answer product surveys?
Keep it short and say so ("2 questions, 30 seconds"), ask in context (in-app, right after a relevant action), and show that past feedback shaped the product. Long generic surveys emailed quarterly are the format users ignore most.