Build a user research synthesis document

Synthesis Turns Interviews into Decisions

Unsynthesized research is research nobody uses. Dovetail's research synthesis writing and Nielsen Norman Group's research methods guidance both note the pattern: teams who skip the synthesis step produce 400 sticky notes and 12 conflicting opinions. The synthesis document — with themes, supporting quotes, conflicting evidence, and product implications — is the artifact that drives decisions.

How the Build a user research synthesis document Prompt Works

The prompt structures synthesis into six sections with explicit requirements — supporting quotes per theme, conflicting evidence per theme, product implications with start/stop/change verbs. The "one theme most likely to be noise" output is the honesty check: every synthesis has a theme that is more artifact than signal.

When to Use It

• You have 10+ interviews and need to produce a decision-grade synthesis.
• Previous syntheses sat in a Notion doc and never drove product changes.
• A leadership review is asking for research-backed recommendations.
• A new PM is learning synthesis discipline.
• Cross-team stakeholders need a concise read of recent user research.

Common Pitfalls

• No supporting quotes. Themes without verbatim quotes are opinions. Every theme needs at least 3 quotes.
• Ignoring conflicting evidence. Themes that don't acknowledge the dissenters are incomplete.
• No product implications. A synthesis without start/stop/change actions is a report, not a decision input.

Sources

• Dovetail Blog — Dovetail
• Which UX Research Methods — Nielsen Norman Group
• Usability Testing 101 — Nielsen Norman Group
• Maze Blog — Maze