User research synthesis
User research synthesis turns raw qualitative data — interviews, workshops, diary studies — into structured findings teams can act on. The aim is not a transcript summary, but evidence-led pain points, themes, and insights that explain what users need and why.
Why it matters
Without synthesis, teams drown in anecdotes or cherry-pick quotes that support pre-existing ideas. Good synthesis clusters related evidence, names themes plainly, and separates confirmed findings from assumptions still to be tested.
Key ideas
- Every finding needs evidence. Pain points should cite quotes or clear references to where they appeared in the source material.
- Insights reframe, not repeat. An insight explains what the evidence means — the underlying need or behaviour — rather than restating the complaint.
- Flag assumptions explicitly. Things the data implies but does not confirm belong in an "assumptions to test" list, not in findings.
- Context matters. Who was interviewed, under what conditions, and what limitations the sample has should be documented upfront.
- Discovery outputs feed definition. Research synthesis is the foundation for problem statements and downstream design work.
How it fits the pipeline
Research synthesis is typically the first structured step in a user-centred design pipeline. Its outputs feed problem definition and everything that follows.
Common mistakes
- Listing quotes without deriving themes or insights
- Presenting team opinions as research findings
- Ignoring contradictory evidence in the transcript
- Skipping caveats about sample size or bias
Further reading (NN/g)
- — how research fits the discover and define stages
- — qualitative methods for understanding user experience over time
- — balancing existing knowledge with primary research
Educational summaries informed by research published by Nielsen Norman Group.