discover-interview-synthesis

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # 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 ## When NOT to Use - You are summarizing one internal meeting for its attendees -> use `foundation-meeting-recap` - You need patterns across multiple meetings over time -> use `foundation-meeting-synthesize` - Your data is survey responses rather than interviews -> use `measure-survey-analysis` - The findings are synthesized and you are ready to frame the problem -> use `define-problem-statement` - You have synthesized findings and want to map them onto a customer's journey across stages and touchpoints -> use `discover-journey-map` ## Instructions When asked to synthesize interview findings, follow these steps: 1. **Gather the Raw Material** Collect all interview notes, transcripts, or recordings. Ensure you have ...