analyzing-user-feedback

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha b7c977844314 · 22 Oct 2026Report an issue or request a re-scan

• Publisherrefoundai GitHub organizationOwner of the repository this skill is read from
• Source folderrefoundai/lenny-skills/skills/analyzing-user-feedbackThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdictb7c977844314A new audit runs when the source changes
• Repository statusNot archivedLast push 97 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Help users convert massive volumes of qualitative and quantitative feedback into high-confidence product decisions through rigorous synthesis and internal immersion.

---
name: analyzing-user-feedback
description: Help users convert massive volumes of qualitative and quantitative feedback into high-confidence product decisions through rigorous synthesis and internal immersion.
---

# Analyzing User Feedback

Transform raw signals into actionable insights by scaling empathy and synthesis.

Help the user with analyzing user feedback using insights from 19 guests and posts across Lenny's Podcast and Newsletter.

## How to Help

1. **Categorize signals** - Help the user group disparate feedback into themes or segments based on user influence and frequency.
2. **Assess representativeness** - Determine if feedback reflects a vocal minority or a broad user need using representation frameworks.
3. **Set up dogfooding** - Design internal processes to experience friction firsthand through audits and mandatory usage programs.
4. **Apply AI synthesis** - Guide the user in using LLMs to process large datasets like transcripts, reviews, and support tickets.

## Core Principles

### Experiential Empathy
Jeff Weinstein: "We show up four to eight people total pretend to be some company with some outcome problem. Rule one is you do not work at Stripe and rule two is we're not here to solve any problems. This is just about practicing empathy for the customer."

Build deeper empathy by having internal teams experience product friction firsthand without the distraction of immediate problem solving.

### Mandatory Service Participation
Keith Yandell: "We have a program called WeDash, where, four times, a year all employees are required to go do deliveries. And I love doing it. I do it more than four times a year, and I usually take my daughters with me."

Require every employee to perform the core service of the business to build authentic empathy and surface operational bugs.

### Creator Mindset Immersion
Maya Prohovnik: "If they talk to users all the time, they see the data, but all of them, once they finally start doing their podcast, they're like, I get it. Something clicked and now I feel like I really understand what they need. And I guess building tools for creators is similar to building a B2B product where you really have to understand business, it's their livelihood."

Directly immerse team members in the product to transform abstract data into a deep understanding of complex user workflows.

### Statistical Representation Filtering
From "What 5 years at Reddit taught us about building for a highly opinionated user base": "Just because someone is loud doesn’t mean you should act on their complaints. You need to get good at identifying whom you should pay attention to. That starts with examining who is being loud."

Evaluate feedback based on its statistical representation and the influence of the users providing it to avoid building for a vocal minority.

## Templates & Frameworks

- **Duolingo Dogfooding Process** (How Duolingo builds product) - A structured internal testing process where every product change goes live to employees before rolling out to users
- **Feedback Evaluation: Representation × Influence Matrix** (What 5 years at Reddit taught us about building for a highly opinionated user base) - A two-factor framework for assessing whether user feedback is worth acting on, based on what percentage of users the feedback represents and whether those users
- **The Trust Vault** (What 5 years at Reddit taught us about building for a highly opinionated user base) - A metaphor and measurement system for tracking how much trust your user base has in you. Trust can be deposited (through wins and transparency) and depleted (th
- **Walk the Store / Essential Journeys Audit** (Katie Dill) - A quarterly process where cross-functional leaders manually test critical user journeys and log friction.
- **Customer Feedback Hub (Coda Template)** (This Week #8: Splitting equity with late-joining co-founders, favorite roadmap templates, and small changes that improve your org) - A Coda template for systematically tracking every piece of customer feedback and following up after improvements are shipped
- **Ramp AI User Personas for PM Feedback** (25 proven tactics to accelerate AI adoption at your company) - AI personas loaded with user research context that give PMs instant feedback on product specs
- **Confluent LLM-Powered Customer Feedback Clustering** (Shaun Clowes) - Confluent uses LLMs internally to semantically cluster inbound customer requests, identify the most popular ideas, and track trending demand over time.
- **WeDash Dogfooding Program** (Keith Yandell) - A mandatory company-wide program requiring all employees to use the product in the real world to build empathy and find bugs.
- **Feedback Prioritization 2×2: Depth of Effect × Breadth of Effect** (What 5 years at Reddit taught us about building for a highly opinionated user base) - A 2x2 matrix for deciding which user feedback to act on, plotting the depth of a feature's impact against how many users it affects.

See `references/artifacts.md` for the full list with details.

## Questions to Help Users

- "What percentage of your total user base does this specific negative feedback represent?"
- "Are you experiencing the product friction firsthand or only viewing it through secondary data?"
- "How does this request align with the needs of your most influential users versus the loudest voices?"
- "What is the current level of trust in your community according to your most recent survey?"
- "Have you analyzed why departing customers feel the product failed its initial promise?"
- "What unique metaphors are users using in their feedback to describe their pain points?"

## Common Mistakes to Flag

- **Building for the vocal minority** - Teams often over-index on the loudest users without verifying if they represent a significant portion of the base.
- **Distracted solutioning during audits** - Discussing solutions too early prevents the team from fully experiencing and documenting the raw friction of the user j

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/refoundai/lenny-skills
git -C lenny-skills checkout b7c977844314

Works in

1. 2026-10-22
   ✓SAFE B 89 / 100

   first audit · source b7c977844314

Questions about analyzing-user-feedback

• github.com/refoundai/lenny-skills/tree/main/skills/analyzing-use — the audited source at commit b7c977844314 and every finding aboveObserved · 22 Oct 2026

Spotted something wrong? Report a correction · Methodology