Discover Interview Synthesis
Scannednpx machina-cli add skill product-on-purpose/pm-skills/discover-interview-synthesis --openclawname: discover-interview-synthesis description: Synthesizes user research interviews into actionable insights, patterns, and recommendations. Use after conducting user interviews, customer calls, or usability sessions to extract and communicate findings. phase: discover version: "2.0.0" updated: 2026-01-26 license: Apache-2.0 metadata: category: research frameworks: [triple-diamond, lean-startup, design-thinking] author: product-on-purpose
Interview Synthesis
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 to Use
- After completing a round of user interviews (typically 5+ participants)
- Following customer discovery calls or sales feedback sessions
- After usability testing sessions to consolidate observations
- When stakeholders need a summary of research findings
- Before ideation sessions to ground the team in user reality
Instructions
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.
Output Format
Use the template in references/TEMPLATE.md to structure the output.
Quality Checklist
Before finalizing, verify:
- Themes are supported by evidence from 3+ participants
- Quotes are verbatim and attributed to participant IDs
- Insights explain "why" not just "what"
- Recommendations are specific and actionable
- Participant identities are protected (no PII)
- Limitations and biases are acknowledged
Examples
See references/EXAMPLE.md for a completed example.
Source
git clone https://github.com/product-on-purpose/pm-skills/blob/main/skills/discover-interview-synthesis/SKILL.mdView on GitHub Overview
Interview Synthesis turns raw user research into structured insights that drive product decisions. It identifies patterns across conversations, connects observations to user needs, and yields concrete recommendations to guide product decisions.
How This Skill Works
Start with gathering all notes, transcripts, and recordings from at least 3 participants. Then create participant profiles, identify recurring themes, and collect representative quotes. Finally, translate themes into insights and actionable recommendations, documenting any limitations.
When to Use It
- After completing a round of user interviews (5+ participants) to identify patterns
- Following customer discovery calls or sales feedback sessions
- After usability testing to consolidate observations
- When stakeholders need a concise, evidence-backed research summary
- Before ideation sessions to ground the team in user needs
Quick Start
- Step 1: Gather raw material (notes, transcripts, recordings) from 3+ participants.
- Step 2: Create participant profiles and tag recurring themes across interviews.
- Step 3: Synthesize themes into insights and actionable recommendations; document limitations.
Best Practices
- Gather data from at least 3 participants to identify patterns and avoid noise
- Tag observations to reveal 3+ recurring themes across participants
- Capture 3–5 verbatim quotes per theme with participant IDs
- Translate themes into insights that explain why they matter for users
- Propose tied, prioritized recommendations with confidence levels and note limitations
Example Use Cases
- Example 1: After 8 interviews for a mobile banking app, synthesized onboarding friction into a top insight and recommended a streamlined signup flow.
- Example 2: In a B2B SaaS study, identified concerns about ROI and security; recommended prioritized features and updated messaging for buyers.
- Example 3: Usability testing of a checkout flow (5 participants) highlighted drop-offs; proposed a single-page checkout with autofill.
- Example 4: Post-release support calls revealed a need for clearer in-app guidance; recommended onboarding prompts and in-app tours.
- Example 5: Early discovery uncovered unclear target personas; proposed refined personas and aligned value propositions for marketing and product teams.