U
user-satisfaction-signals
About user-satisfaction-signals
A design skill for product teams to collect and interpret user satisfaction signals. It covers explicit feedback and behavioral patterns, then turns them into analyses and design artefacts.
Key features
- 01Classifies explicit, implicit, and ambiguous signals
- 02Plans signal collection methods
- 03Interprets behavior by task type
- 04Analyzes trends and user cohorts
- 05Produces satisfaction design artefacts
Use cases
- 01Plan product satisfaction metrics
- 02Map feedback collection touchpoints
- 03Compare new and experienced users
- 04Identify task experience problems
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ owl-listener/ ai-design-skills --skill user-satisfaction-signalsAfter installing, type/user-satisfaction-signalsin Claude Code to confirm it loaded.
Details
From the project READMEUser Satisfaction Signals
Users rarely tell you directly whether they're satisfied. Most satisfaction signals are implicit — buried in behavior patterns that you have to design systems to capture and interpret.
Explicit Satisfaction Signals
These are signals users give intentionally:
- Thumbs up/down: Direct quality rating
- Star ratings: Graded satisfaction
- Written feedback: Comments about what worked or didn't
- NPS or satisfaction surveys: Periodic overall assessment
- Feature requests: Signals of engagement even when expressing a gap
Implicit Satisfaction Signals
These are behavioral signals that indicate satisfaction or dissatisfaction: Positive signals:
- Using the output as-is (no edits)
- Copying the output
- Returning to use the feature again
- Increasing usage over time
- Trying more advanced features Negative signals:
- Regenerating the response (asking the AI to try again)
- Editing the output heavily
- Rephrasing the same request multiple times
- Abandoning mid-task
- Decreasing usage over time
- Switching to manual methods Ambiguous signals:
- Long sessions (engaged or struggling?)
- Many turns (deep work or frustrated iteration?)
- Silence after a response (satisfied or confused?)
Designing Signal Collection
- Instrument the product: Track edits, regenerations, copy events, session duration, and return patterns
- Minimise explicit feedback burden: Don't ask for ratings on every response
- Contextualise signals: A regeneration during creative brainstorming means something different than a regeneration during fact-finding
- Segment by task type: Satisfaction patterns vary by what the user is trying to do
- Combine signals: No single signal is reliable. Look for patterns across multiple signals.
From Signals to Insights
Raw signals need interpretation:
- Signal clustering: Which negative signals appear together? That pattern indicates a specific problem.
- Trend analysis: Are signals improving or degrading over time?
- Cohort comparison: Do new users show different signals than experienced users?
- Correlation with outcomes: Which signals best predict task success or retention?
Design Artefacts
- Signal inventory (explicit and implicit) with collection methods
- Signal interpretation guidelines
- Satisfaction dashboard specifications
- Signal-to-insight analysis frameworks
- Feedback collection touchpoint map
Comments
Markdown supported