Framework · Facilitation techniques · 2 min read
Affinity mapping
Write findings on sticky notes, cluster them silently, then name the clusters as insights, so a group can make sense of research together.
- Brief
Show the question and the rule: one finding per sticky
- Write
Each person writes findings and quotes from the research
- Cluster silently
Everyone moves stickies into groups, without talking
- Name clusters
Write each cluster's name as an insight sentence
- Prioritise
Dot-vote the insights that matter most
About 30–45 minutes in total · works best with 3–8 people per board
Use it when
- You have notes from several user interviews or a usability test, and the team needs to agree what they mean.
- Feedback from many channels (support tickets, surveys, stakeholder comments) needs a structure.
- You run a listening workshop and want to group the pain points people wrote, for example the thorns from Rose, Thorn, Bud.
How to use it
- Prepare the question and the material. Write the research question on the board, for example "What makes planning hard for planners?". Bring the notes, quotes and observations. Output: a board with the question and empty space. 5 minutes.
- Write one finding per sticky. Each person writes findings, quotes or observations, one per sticky, in short sentences. Mark the source (for example "P3") on each. Output: a wall of individual stickies. About 10 minutes.
- Cluster silently first. Everyone moves stickies into groups that feel related, without talking. Anyone can move any sticky. If a sticky keeps moving between two groups, make a copy. Output: rough clusters. About 10 minutes.
- Name the clusters as insights. Now talk. For each cluster, write one sentence that says what it means for the user. Split clusters that hold two ideas. Output: 5–10 named insights. About 10 minutes.
- Prioritise and assign. Use Dot voting to choose the insights that matter most, then name what happens next with each one. Output: a short, ranked list of insights with next steps. About 5 minutes.
Worked example
After 6 interviews with planners who use an internal operations platform, a UX lead runs a 40-minute affinity session with 2 designers, a product manager and a developer. The team writes 70 stickies, clusters them in silence and names five clusters. The top four:
| Cluster (as insight) | Example sticky | Votes |
|---|---|---|
| Planners don't trust the totals, so they recheck in a spreadsheet | "I always export and add it up myself." (P2) | 5 |
| Errors show up only after saving, when it is too late to fix | "It said 'invalid' but not which field." (P5) | 4 |
| Planners filter by date first, not by status | Observed in 5 of 6 sessions | 2 |
| Shift changes lose context | "I write notes on paper for the next shift." (P1) | 2 |
The top two insights become research questions and design work for the next sprint. The product manager owns sharing the board with the other teams.
Watch out for
- Talking while clustering. Discussion too early lets one person shape the clusters. Keep the first round silent.
- Topic labels instead of insights. "Errors" says nothing new. Write what users experience and why it matters.
- Mixing opinions with evidence. Keep stakeholder opinions and research findings on different colours, or on different boards.
- Clustering alone. If the lead clusters alone and presents the result, the team does not own it. Do it together.
Template
Use this structure on a FigJam or Miro board.
AFFINITY MAP About 30–45 min
Research question: _____________________________________
Sources (interviews, tests, tickets): ___________________
Rules: one finding per sticky · mark the source (P1, P2…) ·
cluster in silence · name clusters as insights
Insight 1: _____________________________ votes: __
stickies…
Insight 2: _____________________________ votes: __
stickies…
Top insights → next step (owner):
1.
2.
- GamestormingDave Gray, Sunni Brown & James MacanufoBook · 2010