user-interview-synthesis
User Interview Synthesis Skill
Purpose
Transform raw interview transcripts into a structured synthesis document that surfaces themes, pain points, and actionable insights.
Process
- Read all provided transcripts fully before drawing conclusions
- Identify recurring themes (minimum 3 mentions to qualify as a theme)
- Categorize findings into: Pain Points, Workflow Insights, Feature Requests, Delight Moments
- Select 2-3 verbatim quotes per theme that best represent the pattern
- Draft "So What" implications for each theme — what does this mean for the product?
Output Format
Research Synthesis: [Study Name]
Participants: [n] Date Range: [dates] Research Questions: [list]
Theme 1: [Theme Name]
- Summary (2-3 sentences)
- Supporting quotes
- Implication for product
[Repeat for each theme]
Recommended Next Steps
[Specific, actionable recommendations based on findings]
Quality Checks
- Every theme must be supported by quotes from at least 3 participants
- Implications must connect to product decisions, not just observations
- Avoid researcher bias — let the data lead
More from mohitagw15856/pm-claude-skills
user-research-synthesis
Analyze and synthesize user research findings into structured, actionable insights. Use when given user research data, interview transcripts, survey results, or user feedback that needs to be analyzed and summarised. Produces a themed synthesis with prevalence data, supporting quotes, pain points analysis, feature request prioritisation, and recommended next steps.
26prd-template
Create a Product Requirements Document following proven PM template structure. Use when asked to write a PRD, product spec, feature specification, or requirements document for a new feature or product. Produces a complete PRD with problem statement, user stories, functional requirements, technical considerations, and success metrics.
20stakeholder-update
Create executive stakeholder updates following proven communication frameworks. Use when the user needs to create a status update, progress report, executive summary, or communication for leadership, stakeholders, or executives.
19competitive-analysis
Analyze competitors and create competitive landscape documentation with feature matrices, positioning maps, and strategic recommendations. Use when asked to analyze competitors, create competitive analysis, compare features with competitors, build a competitive landscape, track competitive positioning, or prepare sales battlecard inputs. Produces structured competitor profiles, feature comparison matrix, win/loss analysis, and prioritised strategic recommendations.
18meeting-notes
Structure and format meeting notes following PM best practices. Use when asked to create meeting notes, format discussion notes, capture action items, or document decisions from any meeting type. Produces structured notes with decisions, action items (owner + deadline), open questions, and next steps.
17executive-summary
Write an executive summary for any document, report, or proposal. Use when asked to write an executive summary, management summary, briefing paper, or one-pager for senior stakeholders. Produces a structured summary that busy executives can read in under 3 minutes and act on.
15