Product Feedback Examples (+ Example Feedback Form)

Product feedback is anything a user tells you about your product itself: requests, bugs, usability problems, praise and complaints about features or pricing. Useful product feedback names what the user was trying to do, what happened, and why it matters to them. Below are 12 product feedback examples, grouped by type, an example product feedback form you can copy, and how to respond to each kind.

All examples and the form on this page are illustrative: we wrote them to show the pattern, they are not quotes from real customers. For real, attributed examples from Amazon, Slack, Netflix and others, see 15 customer feedback examples.

This post is part of our customer feedback series. The hub is types of customer feedback. See also how to collect customer feedback and customer feedback analysis.

What makes product feedback useful

Compare two versions of the same request:

• Vague: "Reports are bad."
• Useful: "I export the monthly report to share with my manager, but it doesn't include comments, so I copy them in by hand. Takes me about an hour each month."

The second one has the three parts that matter: the goal (share a report with a manager), the problem (comments are missing) and the impact (an hour a month). Your form and your follow-up questions should pull those three parts out of every piece of feedback.

Product feedback examples by type

Feature request examples

1. Useful: "We'd like to assign a request to a teammate so the right PM gets notified. Right now we tag people in comments and things get missed." Why it works: names the job (route to the owner) and the current workaround.
2. Useful: "Can the widget prefill the user's email? Our users are already logged in and keep typing it again." Why it works: small, specific, and says who is affected.
3. Vague: "Add more integrations." Follow-up to ask: "Which tool do you want connected, and what should happen between them?"

Bug report examples

4. Useful: "Saving a post with an emoji in the title shows 'Something went wrong'. Happens every time, Safari 18 on iPad." Why it works: steps, frequency and environment in one line.
5. Vague: "The app is broken." Follow-up to ask: "What were you doing when it happened, and what did you see on screen?"

Usability feedback examples

6. Useful: "I couldn't find where to change my notification settings. I looked under Profile, then gave up and asked support." Why it works: shows where the user expected it to be.
7. Useful: "The import worked, but I wasn't sure it had finished. No message, the spinner just stopped." Why it works: points at a missing piece of feedback in the UI, not a bug.

Praise examples

8. Useful: "The new filters saved me a lot of time. I used to export everything to a spreadsheet to sort it." Why it works: tells you which change mattered and what it replaced. Praise is feedback too: it tells you what not to break.
9. Vague: "Love it!" Follow-up to ask: "Thanks! What do you use most?"

Pricing and plan feedback examples

10. Useful: "We'd upgrade for SSO alone, but the plan with SSO also includes a lot we won't use." Why it works: names the feature driving the upgrade decision.

Feedback from a lost or churned customer

11. Useful: "We moved because our support team lives in Zendesk and needed to log requests without switching tabs." Why it works: names the missing workflow, which you can check against your roadmap.
12. Vague: "Didn't fit our needs." Follow-up to ask: "What were you hoping it would do that it didn't?"

Example product feedback form

Illustrative example. Adapt the fields to your product.

A good product feedback form is short and pulls out goal, problem and impact. Here is an example you can copy:

Tips for the form:

• Pre-fill what you already know. If the user is logged in, attach their name, email and account instead of asking.
• Keep required fields to four or fewer. Every extra field costs answers.
• Show similar requests. If users can see that someone already asked for the same thing, they vote instead of posting a duplicate.
• Confirm and set expectations. After submitting, say what happens next ("we review new posts every week").

In FeatureOS you can build this as a form in Forms and Surveys, or collect it as posts on a feedback board with custom fields and form templates. Boards suggest similar posts as people type, and the survey generator can draft the questions for you.

Questions to ask for better product feedback

Use these on a form, in a survey or in an interview:

• What were you trying to get done?
• What did you expect to happen? What happened instead?
• How are you working around this today?
• How often does this come up?
• If you could change one thing about [feature], what would it be?
• What almost stopped you from signing up?

More in 11 customer feedback survey questions.

How to respond to product feedback

• Feature requests: thank them, merge with similar requests, and update them when the status changes. A decline with a reason is better than silence; see the art of saying no to feature requests.
• Bugs: confirm you can reproduce it and say when you expect a fix.
• Usability issues: ask if you can watch them do the task; fix the flow, not just the help article.
• Praise: say thanks and ask what they use most.
• Churn feedback: thank them and log the reason; do not argue.

Then analyze the feedback by theme and close the loop when you ship.

Collect and act on product feedback with FeatureOS

FeatureOS gives you a feedback board and in-app widget for requests, forms for structured feedback, AI merge suggestions for duplicates, and a roadmap and changelog to tell customers what shipped. See customer feedback software and feature request software. Plans start at $60/month for 5 seats, and you pay only for team seats. See pricing for details and the 14-day free trial.