Product bay
User interview synthesis
RecipeStableby @julian2026-05-27
Copies
—
loading…
Views
—
loading…
Spice
A bit of context helps. Read the notes.
paste into Claude, or drop the file into a Claude Code skills dir
What it does
Takes messy notes from one or more user interviews and synthesises them into themes, tensions, and clear research implications.
When to use
- After a round of user interviews
- When you have a wall of notes and need to present findings to a client
- As a starting point for a research report or JTBD analysis
The skill
I'm going to paste notes from user interviews. Read everything, then produce:
- Top themes (3–5 max). Each theme needs a name, a one-sentence description, and 2–3 direct quotes that support it.
- Tensions or contradictions. What did different people disagree on? What surprised you?
- What's confirmed. Anything that aligns with existing assumptions.
- What's challenged. Anything that contradicts what we thought we knew.
- Recommended next steps. Two or three specific research or product actions.
Keep themes tight. If a theme appears in only one interview, flag it as a signal rather than a finding. Don't summarise everything, prioritise what's actionable.
Here are the notes:
[paste interview notes]
Comments & reactions
Comments arrive once we point Giscus at the repo. Threads in GitHub Discussions. Reactions count as votes. No new logins.