Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-skills:discover-interview-synthesisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Synthesizes user interview transcripts into structured research findings with themes, quotes, implications, and next steps. Use for analyzing qualitative research and turning raw data into actionable product insights.
Synthesizes user research findings from interviews, surveys, transcripts, and feedback into themes, pain points, feature requests, workflows, and prioritized PM recommendations.
Use this skill when the user asks to "synthesize interview notes", "analyze my user interviews", "what patterns are in my interviews", "help me with continuous discovery", "find the themes in these interviews", "what did I learn from these calls", "turn these interview notes into opportunities", or pastes or shares raw interview transcripts or notes from user conversations. This skill focuses on the interview synthesis step of continuous discovery, not general feedback analysis — use feedback-triage for support tickets or NPS data.
Share bugs, ideas, or general feedback.
An interview synthesis transforms raw user research data into structured insights that drive product decisions. Rather than simply listing what participants said, a good synthesis identifies patterns across conversations, connects observations to underlying user needs, and translates findings into actionable recommendations.
When asked to synthesize interview findings, follow these steps:
Gather the Raw Material Collect all interview notes, transcripts, or recordings. Ensure you have data from at least 3 participants to identify meaningful patterns. Note the research objective and methodology used.
Create Participant Profiles Document each participant with relevant context: their role, segment, tenure, and any notable characteristics. This helps readers assess the representativeness of findings.
Identify Recurring Themes Read through all notes and tag observations by topic. Look for themes that appear across multiple participants (ideally 3+). Distinguish between frequently mentioned topics and one-off comments.
Extract Meaningful Quotes Capture 3-5 verbatim quotes per theme that powerfully illustrate the insight. Good quotes are specific, emotional, or particularly articulate. Always attribute quotes to participant IDs.
Synthesize into Insights Transform themes into insight statements. An insight goes beyond observation ("users mentioned X") to interpretation ("users need Y because of Z"). Connect what you heard to why it matters.
Formulate Recommendations Based on the insights, propose prioritized actions. Each recommendation should tie directly to an insight. Note confidence level based on strength of evidence.
Document Limitations Acknowledge what you didn't learn, sample biases, or areas needing further research. Honest limitations increase credibility.
Use the template in references/TEMPLATE.md to structure the output.
Before finalizing, verify:
See references/EXAMPLE.md for a completed example.