name: 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:
Examples
See references/EXAMPLE.md for a completed example.
1---2name: discover-interview-synthesis3description: <!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->4---5
6<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
7---
8name: discover-interview-synthesis
9description: 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.
10phase: discover
11version: "2.0.0"
12updated: 2026-01-26
13license: Apache-2.0
14metadata:
15 category: research
16 frameworks: [triple-diamond, lean-startup, design-thinking]
17 author: product-on-purpose
18---
19# Interview Synthesis
20
21An 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.
22
23## When to Use
24
25- After completing a round of user interviews (typically 5+ participants)
26- Following customer discovery calls or sales feedback sessions
27- After usability testing sessions to consolidate observations
28- When stakeholders need a summary of research findings
29- Before ideation sessions to ground the team in user reality
30
31## Instructions
32
33When asked to synthesize interview findings, follow these steps:
34
351. **Gather the Raw Material**
36 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.
37
382. **Create Participant Profiles**
39 Document each participant with relevant context: their role, segment, tenure, and any notable characteristics. This helps readers assess the representativeness of findings.
40
413. **Identify Recurring Themes**
42 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.
43
444. **Extract Meaningful Quotes**
45 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.
46
475. **Synthesize into Insights**
48 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.
49
506. **Formulate Recommendations**
51 Based on the insights, propose prioritized actions. Each recommendation should tie directly to an insight. Note confidence level based on strength of evidence.
52
537. **Document Limitations**
54 Acknowledge what you didn't learn, sample biases, or areas needing further research. Honest limitations increase credibility.
55
56## Output Format
57
58Use the template in `references/TEMPLATE.md` to structure the output.
59
60## Quality Checklist
61
62Before finalizing, verify:
63
64- [ ] Themes are supported by evidence from 3+ participants
65- [ ] Quotes are verbatim and attributed to participant IDs
66- [ ] Insights explain "why" not just "what"
67- [ ] Recommendations are specific and actionable
68- [ ] Participant identities are protected (no PII)
69- [ ] Limitations and biases are acknowledged
70
71## Examples
72
73See `references/EXAMPLE.md` for a completed example.
majiayu000