analyzing-user-feedback
Help users synthesize and act on customer feedback. Use when someone is analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Security Assessment
About analyzing-user-feedback
A coaching skill that helps product teams synthesize and act on customer feedback, drawing on techniques attributed to 56 product leaders. It guides the user through a four-step approach: understanding their sources by asking where feedback originates (NPS, support, sales, social, interviews); identifying patterns by clustering feedback into themes and prioritizing by frequency and impact; challenging surface-level interpretations to find root causes rather than stated complaints; and connecting insights to concrete product decisions.
The core of the skill is a set of operating principles distilled from named practitioners. Examples include treating feedback as a continuous river rather than an episodic lake, recognizing that users unintentionally mislead so saying price often means value, clustering by behavioral pathways instead of demographic segments, treating every support ticket as a product failure, attending to silent signals such as ratings not left, filtering the roughly 80 percent of feedback that is legacy-habit noise to find the 20 percent that is gold, aggregating across all channels including what customers are not saying, prioritizing talking to churned users, designing for the larger future audience over a vocal minority, and making insights stick through memorable synthesis.
It supplies a ready list of probing questions to put to the user (where feedback comes from, whether churned users have been interviewed, the root cause behind complaints, whether requests come from early adopters or habit-bound users, and how the insight will be acted on) and a checklist of common mistakes to flag, such as taking feedback literally, listening only to vocal users, ignoring non-users, hoarding insights in silos, and hindsight bias. Use it when analyzing NPS responses, processing support tickets, reviewing user research, or synthesizing feedback across multiple channels. A deeper reference, references/guest-insights.md, collects all 64 insights from the 56 guests, and related skills cover user interviews, product-market fit, roadmap prioritization, and OKRs.
FAQ
When should I reach for this skill?
When you are analyzing NPS responses, processing support tickets, reviewing user research, synthesizing feedback from multiple channels, or trying to identify patterns in customer input.
Does it just take customer feedback at face value?
No. It explicitly pushes you to find root causes rather than stated complaints, noting that users unintentionally mislead, so when they say price they often mean value.
Whose feedback does it emphasize collecting?
It stresses aggregating across all channels and especially interviewing churned users, since the most critical insights often come from people who dropped out of the funnel rather than those who succeeded.
How does it suggest prioritizing conflicting feedback?
Cluster feedback into themes and prioritize by frequency and impact, filter out the roughly 80 percent that is legacy-habit noise, and design for the larger future audience rather than over-indexing on a vocal minority.
Where can I find the full set of expert insights?
All 64 insights from the 56 guests are collected in references/guest-insights.md, referenced as the deep-dive material for the skill.
Install analyzing-user-feedback
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
refoundai/lenny-skills