user-interview-synthesis
This skill transforms raw interview transcripts into structured research synthesis by identifying recurring themes, extracting supporting quotes, and deriving product implications. Use it when analyzing user interview notes, synthesizing qualitative research data, identifying patterns across participant responses, or converting interview findings into actionable product insights. The output includes themed summaries with verbatim quotes from at least three participants, "so what" implications for product decisions, and recommended next steps.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/user-interview-synthesis && cp -r /tmp/user-interview-synthesis/plugins/pm-discovery/skills/user-interview-synthesis ~/.claude/skills/user-interview-synthesisSKILL.md
# User Interview Synthesis Skill Transform raw interview transcripts into a structured synthesis document that surfaces themes, pain points, and actionable insights. ## Required Inputs Ask the user for these if not provided: - **Interview transcripts or notes** (even rough notes work) - **Number of participants and their profiles** (role, company size, context) - **Research questions** (what was the study trying to answer?) - **Date range** of research (for context) ## Process 1. Read all provided transcripts fully before drawing conclusions 2. Identify recurring themes (minimum 3 mentions to qualify as a theme) 3. Categorize findings into: Pain Points, Workflow Insights, Feature Requests, Delight Moments 4. Select 2-3 verbatim quotes per theme that best represent the pattern 5. Draft "So What" implications for each theme — what does this mean for the product? 6. **Validate** — Confirm every theme has quotes from at least 3 participants. Flag any insight resting on fewer as low-confidence. ## Output Structure ### Research Synthesis: [Study Name] **Participants:** [n] **Date Range:** [dates] **Research Questions:** [list] #### Theme 1: [Theme Name] - Summary (2-3 sentences) - Supporting quotes (from at least 3 participants) - Implication for product [Repeat for each theme] #### Low-Confidence Signals (1-2 participants only) [Findings worth tracking but not acting on yet — note what further research would confirm or deny] #### Recommended Next Steps [Specific, actionable recommendations based on findings] ## Quality Checks - [ ] Every theme is supported by quotes from at least 3 participants - [ ] Implications connect to specific product decisions, not just observations - [ ] Researcher bias check: no leading language, findings don't all support one hypothesis - [ ] Single-source signals are flagged separately, not mixed into main themes - [ ] Research questions from the study brief are each addressed (even if the answer is "inconclusive") ## Anti-Patterns - [ ] Do not mix single-source signals into main themes — insights cited by only one participant must be flagged separately - [ ] Do not write implications that are observations restated rather than product decisions enabled - [ ] Do not include themes that only support the project hypothesis — contradictory findings must be surfaced, not omitted - [ ] Do not present findings without quotes — every theme requires verbatim evidence from at least 3 participants - [ ] Do not leave research questions unanswered — each question from the study brief must be explicitly addressed, even if the answer is inconclusive
Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.
Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.
Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.
Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.
Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.