Synthesize Research
When to use
Use this when you have raw qualitative input, interview notes, survey responses, support tickets, sales call notes, and need to turn it into ranked themes with evidence, not a pile of quotes.
Not for: designing the study or interview guide, statistical analysis of quantitative survey data, or generating new ideas from scratch (use pm-brainstorming). If you have not decided what question the research informs, define that first, synthesis without a question produces trivia.
Method
- Confirm the question: what decision does this research inform?
- Code the raw data: tag each observation with the underlying need, pain, or behavior. Keep observations atomic and traceable to source.
- Cluster codes into themes. A theme is a recurring pattern across sources, not one loud voice. Count distinct supporting sources per theme.
- Rank themes by frequency x severity x strategic relevance. Decision point: if a "theme" has one source, it is an anecdote, mark it tentative or drop it.
- Attach evidence: 1-2 verbatim quotes per theme plus counts. Decision point: if the sample is skewed (e.g., only churned users), flag the bias explicitly.
- Translate to implications: what to build, fix, or investigate, with a confidence level.
Example
Question: "Why do trials not convert?" Coding 18 interviews + 40 tickets surfaces theme "setup is confusing" (11 sources, high severity). Quote: "I gave up before importing my data." Contrast: "missing integrations" appeared but only 2 sources, marked tentative. Implication: prioritize guided setup (high confidence); investigate integration demand further (low confidence, thin sample).
Pitfalls
- Inflating one vivid quote into a "theme" without counting sources.
- Ignoring sample bias, generalizing from only churned or only power users.
- Cherry-picking quotes that confirm a prior instead of representing the cluster.
- Stopping at themes without translating them into decisions and confidence.
Output format
# Research Synthesis: [question] — [date]
Sources: [type + counts], sample notes.
## Ranked themes
1. [theme statement] — support: N sources — severity: H/M/L
- "quote 1"
- "quote 2"
## Surprising findings / contradictions
- ...
## Implications
- [action] — confidence: H/M/L
## Gaps
- What the data cannot answer; what to research next.
Low-sample findings marked tentative.
1---2name: pm-synthesize-research3description: Turn raw qualitative input — interviews, surveys, tickets, sales notes — into ranked, evidence-backed themes with source counts, quotes, and confidence-rated implications.4---56# Synthesize Research78## When to use9Use this when you have raw qualitative input, interview notes, survey responses, support tickets, sales call notes, and need to turn it into ranked themes with evidence, not a pile of quotes.1011**Not for:** designing the study or interview guide, statistical analysis of quantitative survey data, or generating new ideas from scratch (use pm-brainstorming). If you have not decided what question the research informs, define that first, synthesis without a question produces trivia.1213## Method141. Confirm the question: what decision does this research inform?152. Code the raw data: tag each observation with the underlying need, pain, or behavior. Keep observations atomic and traceable to source.163. Cluster codes into themes. A theme is a recurring pattern across sources, not one loud voice. Count distinct supporting sources per theme.174. Rank themes by frequency x severity x strategic relevance. **Decision point:** if a "theme" has one source, it is an anecdote, mark it tentative or drop it.185. Attach evidence: 1-2 verbatim quotes per theme plus counts. **Decision point:** if the sample is skewed (e.g., only churned users), flag the bias explicitly.196. Translate to implications: what to build, fix, or investigate, with a confidence level.2021## Example22Question: "Why do trials not convert?" Coding 18 interviews + 40 tickets surfaces theme "setup is confusing" (11 sources, high severity). Quote: "I gave up before importing my data." Contrast: "missing integrations" appeared but only 2 sources, marked tentative. Implication: prioritize guided setup (high confidence); investigate integration demand further (low confidence, thin sample).2324## Pitfalls25- Inflating one vivid quote into a "theme" without counting sources.26- Ignoring sample bias, generalizing from only churned or only power users.27- Cherry-picking quotes that confirm a prior instead of representing the cluster.28- Stopping at themes without translating them into decisions and confidence.2930## Output format31```32# Research Synthesis: [question] — [date]33Sources: [type + counts], sample notes.3435## Ranked themes361. [theme statement] — support: N sources — severity: H/M/L37 - "quote 1"38 - "quote 2"3940## Surprising findings / contradictions41- ...4243## Implications44- [action] — confidence: H/M/L4546## Gaps47- What the data cannot answer; what to research next.48Low-sample findings marked tentative.49```