home / skills / menkesu / awesome-pm-skills / user-feedback-system

user-feedback-system skill

safe

This skill helps you design and implement feedback systems using PMF surveys and user interviews to measure product-market fit and collect insights.

npx playbooks add skill menkesu/awesome-pm-skills --skill user-feedback-system

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.1 KB

---
name: user-feedback-system
description: Builds feedback collection systems using Superhuman's PMF framework and YC's "talk to users" methodology. Use when implementing NPS surveys, scheduling user interviews, or measuring product-market fit.
---

# The Feedback Loop

## When This Skill Activates

Claude uses this skill when:
- Building feedback collection
- Measuring product-market fit
- Implementing user research
- Creating feedback systems

## Core Frameworks

### 1. Superhuman PMF Survey

**The Question:**
> "How would you feel if you could no longer use [product]?"
> - Very disappointed
> - Somewhat disappointed
> - Not disappointed

**PMF Threshold:**
- >40% "very disappointed" = strong PMF
- <40% = need to improve

### 2. Talk to Users (YC)

**The Approach:**
- Talk to users weekly (minimum)
- Ask open-ended questions
- Watch them use product
- Focus on jobs-to-be-done

---

## Action Templates

### Template: Feedback System

```markdown
# Feedback Collection System

## In-App Surveys
**PMF Survey:**
- Trigger: After 2 weeks of use
- Question: "How disappointed if couldn't use?"
- Follow-up: "What's the main benefit?"

**NPS Survey:**
- Trigger: Quarterly
- Question: "How likely to recommend (0-10)?"
- Follow-up: "Why that score?"

## User Interviews
**Cadence:** [Weekly/biweekly]
**Participants:** [How selected]
**Format:**
- 30-minute calls
- Watch them use product
- Ask "why?" 5 times

## Feature Requests
**Collection:**
- In-app widget
- Support tickets
- User interviews

**Tracking:**
- Count: [number of requests]
- Priority: [using RICE]
- Status: [planned/not planned]
```

---

## Quick Reference

### 💬 Feedback Checklist

**Collect:**
- [ ] PMF survey implemented
- [ ] NPS tracking
- [ ] User interview cadence
- [ ] Feature request system

**Act:**
- [ ] Feedback reviewed weekly
- [ ] Patterns identified
- [ ] Prioritized using RICE
- [ ] Closed loop (tell users what you built)

---

## Key Quotes

**YC:**
> "Talk to users. All the time. Until it feels like you're doing it too much."

**Superhuman:**
> "Product-market fit isn't a feeling. It's a number: 40% very disappointed."

Overview

This skill builds repeatable feedback collection systems grounded in Superhuman’s PMF survey and YC’s “talk to users” methodology. It helps teams implement PMF and NPS surveys, schedule and run user interviews, and close the loop on feature requests. The output is a practical, measurable feedback loop you can run weekly or quarterly.

How this skill works

The skill sets up in-app surveys and triggers, defines interview cadence and formats, and creates simple tracking for requests and metrics. It implements the Superhuman PMF question as a core metric, adds NPS monitoring, and embeds a weekly user interview habit to surface qualitative insights. It also provides templates for collection channels, prioritization (RICE), and status tracking to drive decisions.

When to use it

To measure product-market fit quickly with a single clear metric
When you need regular qualitative input through user interviews
To add NPS and quantitative health checks for your product
When launching features and wanting structured feature-request intake
To create a repeatable process for reviewing and acting on feedback

Best practices

Run the PMF survey after ~2 weeks of usage to capture real value perception
Talk to users weekly or biweekly and watch them use the product, not just ask hypotheticals
Follow up PMF answers with an open-ended question: "What's the main benefit?"
Track requests centrally, score with RICE, and review feedback weekly
Close the loop publicly: tell users what you built and why

Example use cases

Add an in-app PMF survey triggered after two weeks to assess early retention risk
Schedule weekly 30-minute user interviews to validate a new onboarding flow
Run quarterly NPS campaigns and analyze verbatim follow-ups for common themes
Collect feature requests via an in-app widget, prioritize with RICE, and publish status updates
Use PMF % very disappointed >40% as a signal to scale growth efforts

FAQ

What exactly is the PMF question I should ask?

Ask: "How would you feel if you could no longer use [product]?" with options: Very disappointed, Somewhat disappointed, Not disappointed.

When should I talk to users versus running surveys?

Surveys give scalable quantitative signals; user interviews provide context and insight. Run both: surveys regularly and interviews weekly to interpret survey trends and uncover root causes.