Synthesis

What Is Synthesis?

Research produces information. Synthesis produces meaning. You talked to five people, read fifty reviews, and analyzed three competitors. Now you have a pile of notes. Synthesis is the act of finding the patterns in that pile — the themes, connections, and insights that tell you what to build.

Synthesis is not summarizing. A summary says "Person A said X, Person B said Y, Person C said Z." Synthesis says "Three out of five people described the same frustration with organizing information across multiple tools. The core tension is between wanting everything in one place and needing different tools for different tasks."

This is where design thinking earns its keep. The ability to see patterns across disparate data points is the skill that separates designers from people who make things look nice.

Synthesis is not about the data you collected. It is about the meaning you extract. Two designers looking at the same research will synthesize different insights — and that is the value.

Affinity Mapping

The most practical synthesis technique is affinity mapping: write each observation on a sticky note (physical or digital), then group related notes together. The groups reveal themes.

Start by spreading everything out. One note per observation, quote, or data point. Do not organize yet — just externalize everything you know.

Then start grouping. Which notes feel related? Pull them together. Give each group a name that describes the theme. "Frustration with manual entry." "Desire for quick capture." "Distrust of automated suggestions."

The group names are your insights. They are more reliable than any single data point because they represent patterns across multiple sources.

Insight Statements

An insight is a concise statement that captures a non-obvious truth about your users. It is not a fact — it is an interpretation of facts that suggests a design direction.

Fact: "Four out of five users said they take photos of recipes from cookbooks." Insight: "Users want to capture recipes in the moment of discovery, not during dedicated organization time. The capture experience must be instant and low-friction."

The insight goes beyond what people said. It explains the underlying behavior and implies what to build. Instant capture. Low friction. These are design requirements that emerged from synthesis, not from a feature request.

Write three to five insight statements. Each should be one to two sentences. Together, they should paint a clear picture of what matters most to your users.

Personas vs. Profiles

Traditional design process creates personas — fictional characters that represent user archetypes. "Sarah, 34, marketing manager, loves cooking but never has time." These can be useful but also dangerously fictitious. You end up designing for an imaginary person instead of real patterns.

A more grounded approach: user profiles based on behaviors, not demographics. "People who collect recipes from multiple sources but never organize them." "People who cook the same five meals and want variety." "People who follow detailed recipes exactly." These describe behavioral patterns, not fictional people.

The question is not "What would Sarah do?" The question is "What do people who exhibit this behavior need?" Behavior-based profiles connect directly to design decisions.

Synthesis with AI

AI is excellent at initial pattern recognition. Feed your research notes to Claude and ask: "What themes emerge from these interview transcripts?" "What are the top pain points mentioned across these reviews?" "Group these observations into categories."

The AI will give you a first pass that is often 70-80% right. Your job is the last 20% — the nuance, the connections the AI missed, the insight that comes from having been in the room when someone's face lit up or fell.

The workflow: let AI do the heavy lifting of organizing and categorizing, then layer your human judgment on top. The AI is a power tool. You are the craftsperson.

From Synthesis to Action

Synthesis is not an academic exercise. It feeds directly into the next steps of the pipeline:

Your insight statements become the basis for Jobs to Be Done (next lesson). "Users want instant capture at the moment of discovery" becomes a job your product must fulfill.

Your themes become feature categories. "Organization is the barrier, not collection" means you build organization tools, not more ways to add recipes.

Your behavioral profiles inform your prioritization. If most users are "collectors who never organize," you design for that reality instead of hoping they will change.

Good synthesis makes every downstream decision clearer. If you find yourself stuck on a feature decision later, go back to your insights. The answer is usually there.