discover-interview-synthesis

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Interview Synthesis
3 
4An 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.
5 
6## When to Use
7 
8- After completing a round of user interviews (typically 5+ participants)
9- Following customer discovery calls or sales feedback sessions
10- After usability testing sessions to consolidate observations
11- When stakeholders need a summary of research findings
12- Before ideation sessions to ground the team in user reality
13 
14## When NOT to Use
15 
16- You are summarizing one internal meeting for its attendees -> use `foundation-meeting-recap`
17- You need patterns across multiple meetings over time -> use `foundation-meeting-synthesize`
18- Your data is survey responses rather than interviews -> use `measure-survey-analysis`
19- The findings are synthesized and you are ready to frame the problem -> use `define-problem-statement`
20- You have synthesized findings and want to map them onto a customer's journey across stages and touchpoints -> use `discover-journey-map`
21 
22## Instructions
23 
24When asked to synthesize interview findings, follow these steps:
25 
261. **Gather the Raw Material**
27…