Synthesis is the process of organizing notes into patterns, themes, and insights the team can use. It typically begins with affinity mapping, which groups observations into themes so patterns emerge more clearly. Affinity mapping is a form of thematic analysis, a qualitative method in which transcripts or notes are coded and grouped into recurring themes and then refined into a coherent narrative of what the data shows. Coding itself proceeds in three steps: open coding labels chunks of data with descriptive codes, axial coding groups codes into categories and explores relationships among them, and selective coding integrates everything into a central theme or theory. To make the coding scheme reproducible, teams measure inter-rater reliability, the degree to which independent coders apply the same codes to the same data, often with a statistic such as Cohen's kappa; higher values mean the scheme is more dependable.
Strong synthesis distinguishes between observations and insights. An observation is a piece of raw data — a quote, a metric, a behavior — while an insight is the meaning or implication that observation carries, often stated as "so what?" plus evidence. A signal is a repeated pattern, quote, or behavior that appears strong enough to influence decisions. Researchers often apply the rule of three: once three independent participants share a pattern with similar language or behavior, it is usually strong enough to surface as a theme rather than being treated as anecdote. An anecdote, in contrast, is a single participant's vivid but unreplicated story; it is useful for empathy and hypothesis generation but not evidence for a finding on its own. Triangulation, combining multiple sources or methods, strengthens confidence in findings and helps guard against the false negative of missing a real insight because of wrong participants, leading questions, or an over-filtered analysis.
Several discipline pitfalls shape synthesis quality. A finding is a pattern supported by evidence (for example, "checkout fails when customers use saved addresses from two countries"), while a recommendation is the team's proposed action in response ("make secondary address editable without re-saving"). How Might We questions reframe findings as open, opportunity-focused prompts, such as "How might we let customers edit a saved address without re-entering it?" that open solution space without committing to a design. Saturation is the point where additional interviews produce few genuinely new themes; it is the qualitative analogue to a sufficient sample size and protects against both under- and over-investment in interviews. The recency effect is a bias where the most recent interviews weigh disproportionately in synthesis, even if earlier participants had more relevant experience; the antidote is to re-read all notes rather than only the latest ones. Strong synthesis also avoids the false positive, a conclusion that feels compelling but is actually based on weak or unrepresentative evidence, and explicitly notes the difference between a feature request — a specific solution the customer proposes — and a need, the underlying job or outcome, since the same need often yields many different feature requests across customers.