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

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 data from at least 3 participants to identify meaningful patterns. Note the research objective and methodology used.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. 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. A complete synthesis fills every template section: Research Overview; Key Themes; Notable Quotes; Insights; Recommendations; and Appendix.

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.

Scenario: 5 onboarding interviews for a team scheduling tool

This is the INPUT brief for an output-quality eval. The skill arm and the control arm each receive everything below (and nothing else about how to do the work) and produce an interview-synthesis artifact for it. Judges never see this header. The input is RAW interview notes; synthesis is the skill's job.

Research context

Product: a team scheduling / shift-planning tool for hourly workforces (retail, hospitality). Research goal: understand why new manager accounts often go quiet in the first two weeks. Method: 5 remote interviews with managers who signed up in the last 30 days, ~30 min each.

Raw notes by participant

P1 - cafe manager, 8 staff, signed up but barely used:

• "I built the first schedule and then my staff didn't see it. Turns out they never downloaded the

app, so I just went back to the group chat."

• Spent 40 min on the first schedule. "It was fiddly but fine once I got it."
• Didn't know there was a way to send a text invite to staff.

P2 - retail shift lead, 22 staff, active:

• "The import from my spreadsheet saved me. If I'd had to type 22 people in I'd have quit."
• Wants the staff to confirm shifts. "Half the value is knowing they actually saw it."
• "Honestly the notifications are the whole product for me."

P3 - restaurant owner, 15 staff, churned:

• "I couldn't tell if it was sending texts or not. I sent a schedule and three people said they never

got it, so I stopped trusting it."

• Found settings confusing. "Too many toggles I didn't understand."

P4 - gym manager, 6 staff, active but frustrated:

• "Setup took a whole evening. Adding people one by one was painful."
• "Once it's set up it's great, but getting there is the problem."
• Loves that staff can swap shifts.

P5 - hotel front-desk supervisor, 30 staff, quiet after week 1:

• "My staff are older and not all of them have smartphones, so the app-only thing didn't work for a

chunk of my team."

• "I needed a printable version and couldn't find one fast."
• Did say the schedule builder itself was "the best one I've tried."

What the team wants from the synthesis

Patterns across participants, evidence-backed insights, and prioritized recommendations for the onboarding experience. The audience is the product team and the head of growth.

discover-interview-synthesis - Version History

2.1.0 (2026-06-10)

Quality-convergence minor (F-12 Batch 3): added a "When NOT to Use" section with boundary pointers to neighboring skills, and the Output Format now enumerates the template sections a complete artifact fills. No template or example changes.

2.0.1 (2026-06-10)

Description-only patch (F-12 Batch 0, from the 2026-06-09 repo audit): the trigger-surface description was rewritten to disambiguate collision pairs with an explicit boundary pointer to the sibling skill. No body, template, or behavior changes.

2.0.0 (2026-01-26)

Baseline row for the prior published version; see git history for its changes.

Interview Synthesis: New User Onboarding Experience

Research Overview

Objective

Understand why only 34% of new users complete onboarding and identify friction points preventing users from reaching their "aha moment" within the first 7 days.

Methodology

• Format: Video calls via Zoom
• Duration: 45 minutes average
• Interviewer(s): Sarah Chen (Product), Marcus Williams (UX Research)
• Date Range: January 2 to January 10, 2026

Participant Summary

Key Themes

Theme 1: Overwhelming Initial Setup

Prevalence: 5 of 5 participants

Summary: Every participant described feeling overwhelmed when first logging in. The dashboard presented too many options without clear guidance on where to start. Users who successfully onboarded found their own path through trial and error, while churned users gave up when they couldn't figure out the first step.

Evidence:

• P1: "I logged in and just stared at the screen. There were like fifteen buttons and I had no idea which one to click first."
• P2: "I spent 20 minutes trying to figure out how to create my first project. In Asana, it was obvious. Here, I felt lost."
• P5: "I'm pretty tech-savvy and even I was confused. If I can't figure it out quickly, my team definitely won't."

Theme 2: Missing Context for Features

Prevalence: 4 of 5 participants

Summary: Users didn't understand why they should use specific features or how they fit into their workflow. Features were explained in terms of what they do, not why they matter. Users skipped important setup steps because they didn't understand the value.

Evidence:

• P3: "I eventually figured out the workspace settings, but I almost skipped it. Nothing told me why I should care about configuring those options."
• P4: "There's a tutorial that shows you where to click, but not why. I need to know if this will save me time before I invest effort setting it up."

Theme 3: Desire for Quick Wins

Prevalence: 4 of 5 participants

Summary: Users wanted to accomplish something meaningful within the first 10 minutes. Those who could create a simple project and invite a colleague felt confident about continuing. Those who got stuck in setup without visible progress abandoned the product.

Evidence:

• P1: "I just wanted to get one thing done to see if this tool works for me. But I couldn't even figure out how to add a simple task."
• P3: "What kept me going was when I finally created a project and invited my teammate. That 5-minute demo with her sold me on the tool."
• P5: "I have 30 tools fighting for my attention. If I can't see value in 10 minutes, I'm moving on."

Theme 4: Team Invitation Friction

Prevalence: 3 of 5 participants

Summary: Users who wanted to evaluate the tool with their team encountered friction when inviting colleagues. The invitation flow required too much information upfront and didn't provide sample content for the team to explore together.

Evidence:

• P2: "I wanted to show my team, but the invite form asked for everyone's job title and department. That felt like too much work for a trial."
• P4: "I invited my team but they logged into an empty workspace. I had to walk them through everything on a call because there was nothing to explore."

Notable Quotes

"I logged in and just stared at the screen. There were like fifteen buttons and I had no idea which one to click first." - P1, Marketing Manager, Day 3 of trial

"If I can't see value in 10 minutes, I'm moving on. I have 30 tools fighting for my attention." - P5, Product Manager who churned

"What kept me going was when I finally created a project and invited my teammate. That 5-minute demo with her sold me on the tool." - P3, Team Admin who completed onboarding

"There's a tutorial that shows you where to click, but not why. I need to know if this will save me time before I invest effort setting it up." - P4, Operations Director

"I'm pretty tech-savvy and even I was confused. If I can't figure it out quickly, my team definitely won't." - P5, Product Manager who churned

Insights

Insight 1: Users need guided first steps, not feature tours

Users don't want to learn about all features - they want to accomplish their first goal. The current onboarding treats all features equally, overwhelming users with options. Successful users found their path by ignoring most of the interface and focusing on one task. We need to guide users to that first success rather than showing them everything.

Implication: Replace the current feature tour with a goal-oriented wizard that asks users what they want to accomplish and guides them to that specific outcome.

Insight 2: Value demonstration must precede feature explanation

Users skip features when they don't understand the benefit. Current tooltips explain mechanics ("Click here to set due dates") but not value ("Never miss a deadline again"). Users who completed onboarding discovered value through experimentation; we shouldn't require that effort.

Implication: Reframe all onboarding copy to lead with benefits. Use social proof ("Teams using this feature complete projects 20% faster") to motivate feature adoption.

Insight 3: Collaborative trial experiences drive conversion

Users who invited teammates and had a shared experience were significantly more likely to continue. Individual evaluation feels like work; collaborative exploration feels like progress. The current invitation flow adds friction instead of facilitating team discovery.

Implication: Optimize the invite flow to be frictionless (email-only) and pre-populate shared workspaces with sample content that teams can explore together.

Recommendations

Recommendation Details

1. Implement Guided First-Project Wizard

Replace the current dashboard landing with a 3-step wizard that asks users to: (1) name their first project, (2) add 2-3 sample tasks, and (3) set a due date. This creates an immediate quick win and teaches core functionality through doing rather than watching.

Next steps: Design sprint with UX team, prototype by end of month, A/B test against current onboarding.

2. Add Sample Project for Team Exploration

When a user invites teammates, automatically create a sample project called "Getting Started Together" with pre-populated tasks that demonstrate collaboration features. Include tasks like "Comment on this task" and "Assign yourself something."

Next steps: Define sample project content with Customer Success team who knows what drives adoption, implement as part of invitation flow enhancement.

Appendix

Methodology Notes

Participants were recruited from users who signed up in the last 30 days. We intentionally included both completed onboarding and churned segments to understand both success and failure paths. Interviews were semi-structured with core questions about first impressions, confusion points, and decision factors.

Limitations

• Sample skewed toward individual contributors and managers; no C-level executives interviewed
• All participants were from companies with 10-50 employees; enterprise experience may differ
• Did not include users who never logged in after signup (a significant segment)
• Self-reported friction may differ from actual behavior; recommend supplementing with session recordings

Raw Notes

Detailed interview transcripts stored in Notion: [Research Repository / 2026-Q1 / Onboarding Study]

Interview Synthesis: [Research Topic]

Research Overview

Objective

<!-- What question(s) were you trying to answer? -->

[Research objective]

Methodology

<!-- How were interviews conducted? -->

• Format: [In-person / Video call / Phone]
• Duration: [Average interview length]
• Interviewer(s): [Names or roles]
• Date Range: [Start date] to [End date]

Participant Summary

Key Themes

Theme 1: [Theme Title]

<!-- Theme mentioned by X of Y participants -->

Prevalence: [X] of [Y] participants

Summary: [2-3 sentences describing the theme]

Evidence:

• P1: "[Quote]"
• P3: "[Quote]"
• P5: "[Quote]"

Theme 2: [Theme Title]

Prevalence: [X] of [Y] participants

Summary: [2-3 sentences describing the theme]

Evidence:

• P2: "[Quote]"
• P4: "[Quote]"

Theme 3: [Theme Title]

Prevalence: [X] of [Y] participants

Summary: [2-3 sentences describing the theme]

Evidence:

• P1: "[Quote]"
• P2: "[Quote]"
• P3: "[Quote]"

Notable Quotes

<!-- 5-8 particularly powerful or illustrative quotes -->

"[Quote that captures a key insight]" - P[X], [Context]

"[Quote that captures a key insight]" - P[X], [Context]

"[Quote that captures a key insight]" - P[X], [Context]

Insights

Insight 1: [Insight Statement]

<!-- Insights explain WHY, not just WHAT -->

[Explanation of what this means and why it matters. Connect observations to underlying user needs or motivations.]

Implication: [What this means for product/design decisions]

Insight 2: [Insight Statement]

[Explanation of what this means and why it matters.]

Implication: [What this means for product/design decisions]

Insight 3: [Insight Statement]

[Explanation of what this means and why it matters.]

Implication: [What this means for product/design decisions]

Recommendations

<!-- Prioritized actions based on insights -->

Recommendation Details

1. [Recommendation Title]

[Detailed description of what to do and why. Include specific next steps.]

2. [Recommendation Title]

[Detailed description of what to do and why. Include specific next steps.]

Appendix

Methodology Notes

<!-- Any relevant details about how research was conducted -->

[Additional methodology details if needed]

Limitations

<!-- Acknowledge biases, gaps, or constraints -->

• [Limitation 1: e.g., sample skewed toward power users]
• [Limitation 2: e.g., did not include churned customers]
• [Areas for further research]

Raw Notes

<!-- Link to or include abbreviated raw notes by participant -->

[Link to detailed notes or indicate where they're stored]