What it is
The gathering and synthesis of feedback that users volunteer through support tickets, reviews, in-product prompts, and social channels, turning a steady stream into themes.
When to use it
During Implement, continuously, as an always-on signal of real-world pain points and sentiment.
Why (value)
Captures real problems in users’ own words at the moment they occur, cheaply and continuously.
How to run it
- Identify the channels where feedback arrives.
- Centralize and tag incoming feedback.
- Code it into themes and track frequency.
- Flag severe or spiking issues.
- Route insights to the backlog and close the loop.
Inputs and outputs
- Inputs: Access to feedback channels and a tagging scheme.
- Outputs: Themed issues, sentiment trends, and priorities.
Time and effort
Low per item, ongoing in aggregate.
Evidence and limitations
Volunteered feedback is direct-user but self-selected: the loudest and most dissatisfied are overrepresented, so it skews and is not a representative sample. See Evidence and limitations.
Tips and pitfalls
- Remember who does not bother to write in.
- Separate frequency from severity.
- Close the loop so feedback keeps coming.
Variations
Support-ticket mining, review analysis, in-product feedback widgets, and social listening.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- NN/g, “Open-Ended vs. Closed Questions in User Research.”
Explore related methods
- Surveys — Ask a defined set of questions to many people to measure attitudes and self-reported behavior at scale.
- Analytics review — Examine real usage data to see what large numbers of users actually do.
- Interviews — Talk with users one on one to understand their goals, context, and reasoning in their own words.
