← ClaudeAtlas

analyzing-user-feedbacklisted

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.
TindanLawrence/lenny-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill TindanLawrence/lenny-skills
# Analyzing User Feedback Help the user extract actionable insights from customer feedback using techniques from 56 product leaders. ## How to Help When the user asks for help analyzing feedback: 1. **Understand their sources** - Ask where feedback is coming from (NPS, support, sales, social, interviews) 2. **Help identify patterns** - Assist in clustering feedback into themes and prioritizing by frequency and impact 3. **Challenge surface-level interpretations** - Push them to find root causes, not just stated complaints 4. **Connect to action** - Help translate insights into product decisions ## Core Principles ### Feedback is a river, not a lake Shaun Clowes: "Really smart product managers are constantly swimming in a feedback river. Set up streams of user interview data, NPS, and competitor info to wash over you daily." Make feedback consumption continuous, not episodic. ### Users lie (unintentionally) Bret Taylor: "Taking what a customer says in a focus group is rarely correct. Practice intellectual honesty to distinguish surface-level complaints from root causes." When users say "price," they often mean "value." ### Cluster, don't segment Bob Moesta: "Instead of segmenting by demographics, we cluster by behavioral pathways. It's not one reason why people do things—it's sets of reasons." Look for the 'hire and fire' criteria for different user clusters. ### Every support ticket is a product failure Geoff Charles: "We literally have 'every support ticket is a fai