User Interview Synthesis
Analyze interview data and extract insights
- • Clear themes with evidence: frequency counts and representative quotes (not vibes).
- • Links to Jobs‑to‑Be‑Done (functional, emotional, social) so decisions make sense.
- • Traceability: each insight maps back to specific participants and notes.
- • Actionability: "How Might We" questions and next steps—prototype, validate, measure.
- • Prioritization: severity × frequency × business value with explicit confidence.
- • Cherry‑picking memorable quotes without checking how often it happens.
- • Vague themes (e.g., "Users want simplicity") with no product implication.
- • Jumping to personas too early; ignore behaviorally distinct patterns.
- • Failing to look for evidence that challenges the main themes.
- • Delivering a beautiful readout with zero next actions or owners.
I have 10 messy transcripts. Where do I even start?
Timebox a first pass: highlight pain points, outcomes, and workarounds. Tag quotes, not opinions. Then affinity map: cluster tags until patterns emerge. You're looking for repetition and tension, not poetry.
How many interviews are "enough" before I see real patterns?
There is no fixed interview count that guarantees you have heard the important themes. Review how much new information each interview adds and whether relevant customer groups are represented.
Theme vs insight—what's the difference?
Theme: a repeated pattern (what happens). Insight: the "so what" (why it matters + implication). Good insights produce a crisp HMW and a decision (prototype, measure, or punt).
How do I avoid confirmation bias when picking quotes?
Keep a quotes database with counts per theme, counter-examples, and confidence notes. A second researcher can independently review a subset.
Where does Jobs‑to‑Be‑Done fit in?
Use JTBD as a lens to explain behavior: functional job, emotional relief, social signaling. Map key quotes to jobs. It turns "feature requests" into real progress customers are trying to make.
What do I hand off to stakeholders without a 30‑page deck?
A one‑pager: top 3–5 themes with frequency, 3 killer quotes, 2–3 HMWs, and a next‑step plan (prototype, metric, owner, date). Put the quotes database and notes in the appendix for the curious.
How do I prioritize opportunities from interviews?
Compare severity, frequency in the interviewed sample, business impact, and confidence. Keep rare but potentially serious findings visible for further research.
We heard one wild outlier. Chase it or ignore it?
Neither. Park it in "emerging signals" and validate cheaply—mini survey, concierge test, or a prototype thread. Don't let one quote set your roadmap, but don't lose potential wedges either.
Should we create personas from this round?
Create personas when consistent behavioral clusters affect your decisions. Otherwise, group findings by task or customer segment and keep only the distinctions supported by the research.
How do I make this useful for engineers?
Translate insights into behaviors and constraints: "Users abandon after 2nd step when docs are missing; need offline draft + autosave." Add HMWs, acceptance tests for prototypes, and the top 3 quotes that humanize the problem.
When to use it
Qualitative research synthesis
Before you use the output
- •Fill in the variables with the facts and constraints you have.
- •Check the output against your source material and revise any mistakes.
- •Add relevant context when the first draft misses part of your task.
Expected output
Research insights report