Affinity Mapping: Turning Interview Notes Into Patterns

What Affinity Mapping Actually Solves

After six or seven interviews you'll have pages of notes, and no individual note tells you much on its own. Affinity mapping is a simple technique for surfacing the patterns hiding across all of them: you write every observation on its own note, then group notes that feel related until themes emerge from the bottom up, instead of forcing your notes into categories you decided on beforehand.

The bottom-up part is what makes it work. If you start with predefined categories, you'll unconsciously sort notes to fit them and miss the theme you didn't expect to find.

Running an Affinity Mapping Session

Start by pulling every distinct observation from your interview notes onto its own sticky note or digital card — one observation per note, written as close to the participant's own words as possible. A single 30-minute interview typically produces 15 to 25 notes.

With all notes on a board, begin grouping ones that feel related, without labeling the groups yet. Move notes freely; a note that seems to belong in one cluster might make more sense in another once more notes are added. This is naturally a bit messy, and that's fine — clarity comes from the process, not from planning the structure in advance.

Once clusters stabilize, write a short label for each one that captures the shared theme, phrased as an insight rather than a topic. "Search" is a topic; "Users abandon search after one failed attempt and switch to browsing instead" is an insight. The second version tells you something you can design against.

From Clusters to Insights

Not every cluster deserves equal weight. Rank your clusters by two factors: how many separate interviewees contributed notes to it, and how strongly participants expressed it (a passing comment versus a recurring frustration). The clusters that are both frequent and strongly felt are your priority themes — these are what should shape your problem statements and, eventually, your wireframes.

It helps to write each priority theme as a single sentence that a teammate who wasn't in the interviews could understand and act on. If a cluster can't be summarized that clearly, it likely needs another look before you build design decisions on top of it.

Practical Review Checklist

Before moving from research into design, confirm that you can:

• Trace every theme back to notes from more than one interview
• State each priority theme as an insight sentence, not a single word
• Rank themes by both frequency and intensity, not just note count
• Identify which themes conflict with the team's initial assumptions
• Share the affinity map with someone outside the research and have it make sense

Conclusion

Affinity mapping turns a stack of individually unremarkable notes into a short, defensible list of themes. That list — not the raw interview transcripts — is what should drive your next design decisions, because it represents what was actually common across real users rather than what stood out to you personally.