Product feedback questions to ask users
The best feedback questions ask about what someone did, not what they think — because a user who says the product is 'great' and a user who opened it once this month are often the same person. These 35 questions are built to get past the polite answer.
Product managers, founders, and customer-success leads collecting feedback from existing users — they spend their days watching adoption dashboards, fielding feature requests from sales and support, and trying to work out which of the loud asks reflect a quiet majority.
- What they're trying to learn
- understand what users actually get from the product, where it fails them, and what would make them use it more — in their words, with enough detail to act on.
- Who they interview
- current users, from the very active to the recently lapsed
Use this after someone has used the product for real — a few weeks in, at renewal, after a big release, or when usage drops. It works as a 20-minute call script or, trimmed to a dozen questions, as a survey. Pair it with the customer interview template for discovery with prospects.
Product feedback questions to copy & run
First use & onboarding
- 1.What were you trying to get done the first time you opened the product?
- 2.Walk me through that first session. Where did you get stuck, if anywhere?
- 3.How long did it take before it did something useful for you?
- 4.What almost made you give up, if anything?
- 5.Was there something you expected it to do that it didn't?
Everyday use & value
- 1.When did you last use it, and what for?
- 2.What's the one thing you use it for most?
- 3.What would you do instead if it disappeared tomorrow?
- 4.Which part of your week does it make easier — and by how much?
- 5.Who else on your team uses it, and what do they use it for?
- 6.How would you describe it to a colleague in one sentence?
Friction & frustration
- 1.What's the most annoying thing about using it?
- 2.The last time it didn't do what you wanted, what happened?
- 3.What do you do outside the product to work around something it can't do?
- 4.Is there anything you do in it that feels like more steps than it should be?
- 5.What have you stopped using, and why?
- 6.Where do you not trust what it shows you?
Missing features & requests
- 1.If you could change one thing, what would it be — and what would that let you do?
- 2.What have you asked us for before that never arrived?
- 3.Is there a tool you use alongside it that you wish it replaced?
- 4.What's the last thing you wished it could do, in the moment you wished it?
- 5.Of the things you've mentioned, which would you give up the others for?
Pricing & value for money
- 1.Does what you pay feel right for what you get? What would make it feel cheap, or expensive?
- 2.If the price doubled, what would you do?
- 3.What would have to be true for you to move to a bigger plan?
Churn & loyalty
- 1.Have you considered switching to something else? What prompted it?
- 2.What would make you leave?
- 3.What's kept you, so far?
- 4.How likely are you to recommend it, and what would you say if you did?
- 5.If a competitor launched tomorrow, what would they have to do better?
Wrap-up
- 1.What should I have asked you that I didn't?
- 2.Who else on your team should I talk to?
- 3.Can I come back to you when we've built something from this?
Tips for better answers.
- Ask about the last time, not usually. 'When did you last use it?' gets a date; 'How often do you use it?' gets a flattering estimate.
- Separate the complaint from the request. Users describe solutions ('add an export button'); your job is to find the problem behind it ('I don't trust the in-app numbers').
- Talk to lapsed users, not only fans. The people who quietly stopped using it know things your power users don't.
- Weight by evidence, not volume. Three users with the same workaround outweigh one loud feature request — if you can show the three.
- Close the loop. Tell people what you built from their feedback; they will give you better feedback next time.
Questions about this template.
What are the best product feedback questions to ask users?
Ones about behavior rather than opinion: when they last used the product and for what, what they do when it fails them, what they do outside it to work around gaps, and what would make them leave. 'Do you like it?' produces politeness; 'What did you do the last time it didn't work?' produces a finding.
How many feedback questions should I ask?
For a call, 8–12 from this list fills 20 minutes with follow-ups. For a survey, no more than 6–8, mostly open-ended, or completion drops. Pick from the sections that match what you need to learn rather than running the whole template.
What is the difference between product feedback questions and customer interview questions?
Feedback questions are for people already using the product and are about their experience of it. Customer interview questions are for discovery — understanding a problem and how people handle it today, with or without your product. Use the customer interview template for prospects and this one for users.
How do I analyze product feedback from many users?
Record and transcribe the calls, tag each pain point, request, and workaround with the quote behind it, and group what repeats across users into themes. Intervool does that automatically for feedback calls and interviews and carries the themes into a prioritized roadmap, so the feedback changes what gets built.
Don't just ask the questions — synthesize the answers.
Save these questions as a template in Intervool, capture the interview, and let AI turn every conversation into insights, personas, and a prioritized roadmap. Free for 14 days.