User Feedback
User feedback is any information users share, directly or indirectly, about their experience with a product.
Solicited versus unsolicited
| You asked for it | It arrived on its own |
|---|---|
| A user interview | A support ticket |
| A cancellation survey | A public review |
Both are user feedback. The unsolicited kind is often the most honest.
What is User Feedback?
User feedback is any information a user gives you, directly or indirectly, about their experience with your product.
Practitioners generally split it two ways. ProductPlan defines the first split plainly: "solicited feedback is what you get when you deliberately request someone to share their opinions," while "unsolicited feedback is what you get when you have provided data without specifically being requested; it is observed." Solicited feedback comes from something you triggered, an interview or an in-app prompt. Unsolicited feedback shows up on its own, in a support ticket or a public review nobody asked for.
The second split is qualitative versus quantitative. Nielsen Norman Group frames these as complementary, not competing: qualitative research "informs the design process," while quantitative research "provides a basis for benchmarking programs and ROI calculations." A five-minute call that surfaces why a user is confused is qualitative. A dashboard tracking how many users hit that same confusing step is quantitative. Both matter, and neither replaces the other.
Marty Cagan pushes the definition further in his writing for the Silicon Valley Product Group: most teams collect feedback but avoid the feedback that stings. He opens with Elon Musk's line that "it is very important to actively seek out and listen very carefully to negative feedback," then makes his own case for why: "so far I haven't found anything that can compare to the qualitative feedback we get when we sincerely try to figure out why a person won't use or buy our product." That's the definition Produck builds around. User feedback isn't a satisfaction score you collect to feel good. It's raw signal about why people don't get value yet, and going and getting the uncomfortable version of it on purpose is the actual skill.
Why it matters for product-market fit
User feedback is the raw material of the Feedback Loop, the mechanism that turns what users say into what you actually build. Produck's own loop runs Listen, Diagnose, Decide, Ship, and user feedback is the entire input to the first stage. If Listen is broken, everything downstream is guessing.
Most teams don't have a Listen problem because feedback is scarce. They have one because it's scattered. A support ticket in Zendesk, a comment on a cancellation survey, a line in a sales call transcript, a Slack message from a customer success manager, none of it in one place, none of it comparable to the rest. Feedback Triage is what turns that pile into something a team can act on: grouping raw feedback by theme so Diagnose has something coherent to work with instead of a hundred disconnected complaints.
Feedback also isn't a substitute for talking to people. A User Interview gets you context that a feedback form never will, the "why" behind the "what." Produck treats structured feedback capture and direct conversation as two inputs to the same pipeline, not competing methods.
The stakes are real. We've written before about why most teams still haven't found product-market fit despite running every framework in the book, and the pattern is almost always the same: feedback exists, it's just never turned into a decision. Product-Market Fit isn't a survey score you hit. It's the compounding result of closing this loop faster than your competitors close theirs, and user feedback is what feeds it.
When it works, and when it doesn't
It works when
- The feedback gets routed somewhere it can be acted on, not just logged and forgotten
- You're actively pulling negative and critical feedback, not only the feedback that arrives on its own
- Qualitative signal (why) and quantitative signal (how many, how often) are read together, not in isolation
- Someone owns turning feedback into a shipped decision, closing the loop back to the users who gave it
It falls short when
- It's collected as a vanity metric, a score to report upward, with no path to a product decision
- It's treated as a replacement for talking to users directly rather than a complement to it
How to apply it
- Pick two sources you already have, support tickets and a cancellation survey, and pull the last month of raw entries into one place.
- Tag each entry as solicited or unsolicited so you know which ones you asked for and which arrived on their own.
- Group entries by the underlying problem, not by the words used, since ten different phrasings often point at one root cause.
- Actively go looking for the feedback nobody volunteered: call a user who churned last month and ask what almost worked.
- Take the top pattern that surfaces and turn it into one concrete product decision before the week ends.
- Close the loop by telling the users who gave that feedback what changed, so the next round of feedback keeps coming.
Frequently asked
How do you receive feedback from users?
Users hand you feedback two ways: solicited, where you deliberately request it through interviews or in-app prompts, and unsolicited, where it arrives on its own through support tickets or public reviews. Most teams only monitor the unsolicited channel, which means they miss the feedback that never gets volunteered.
What is the best way to collect user feedback?
Combine active outreach with passive capture: schedule direct conversations with users who churned or almost churned, and route every support ticket and in-app comment into one shared place. Marty Cagan's SVPG article on discovery feedback opens with a line from Elon Musk about how important it is to actively seek out negative feedback, and Cagan argues the same point: the critical feedback teams avoid asking for is the most valuable kind, so the best collection method is the one that goes looking for it rather than waiting for it.
Sources
- Customer Feedback | Definition and Overview, ProductPlan
- Qualitative vs. Quantitative UX Research, Nielsen Norman Group
- Discovery: Feedback, Marty Cagan, Silicon Valley Product Group