A synthesis method where observations, quotes, and ideas from research sessions are written on individual notes and grouped by thematic similarity. The resulting clusters surface patterns across many data points, helping teams move from raw research to actionable insights without losing the nuance of individual observations.
Common contexts
- Synthesizing notes from 8 user interviews into problem clusters before a design sprint
- Grouping stakeholder workshop outputs to find shared priorities across departments
- Organizing usability test observations into recurring failure patterns to prioritize fixes
Use when
Run an affinity map when you have more than 5 hours of research data and need the whole team aligned on what it means — not just the researcher. It's most effective when done collaboratively within 48 hours of fieldwork, while observations are still fresh enough to discuss.
Avoid when
Affinity mapping done by one person in isolation defeats the purpose — you lose the shared understanding that makes it powerful. It also creates false confidence when used too early, before enough data has been gathered to find genuine patterns rather than just reflecting the researcher's existing assumptions.
The insight isn't in the stickies — it's in the arguments you have while grouping them. Disagreements about where a note belongs reveal assumptions the team didn't know it was holding.
Real-world examples
- IDEO used affinity mapping to cluster hundreds of field observations from hospital patients into themes that shaped a new ER check-in experience.
- Spotify's research team groups post-interview sticky notes by theme on a Miro board to surface patterns across participant responses.
- Google Ventures Sprint teams use affinity mapping on day one of a sprint to align on problem areas before voting on the focus.