Affinity mapping: how to turn a wall of sticky notes into decisions

Affinity mapping works when you finish with findings and actions: one observation per note, sort silently, count people instead of notes, then agree what to do.

Instant Expert EditorialPublished Updated 6 min read

Affinity mapping is a good way for a team to agree on what a round of interviews taught them, as long as you finish with findings and actions instead of a wall of clusters. You write each observation on a sticky note, group related notes, then work out what each group means. Nielsen Norman Group defines affinity diagramming as organizing related observations, ideas or findings into distinct clusters (it is also called affinity mapping, collaborative sorting or snowballing). The American Society for Quality says the method, also known as the KJ method, was created in the 1960s by the Japanese anthropologist Jiro Kawakita.

For interview research there are four passes: pull observations out of your notes, sort them, decide what each group tells you, and agree what to do next.

Use it when nobody can hold all the notes in their head

ASQ recommends affinity diagrams when facts or ideas seem chaotic, when an issue is too large to grasp and when group consensus matters. It says they tend to have 40 to 60 items, though 100 to 200 isn't unusual.

GOV.UK's service manual recommends analyzing as soon as you can after each round, inviting everyone who observed and allowing about one hour of analysis for every two hours of research.

The example: returns software for retail chains

Here is a made-up example. A startup building returns software for specialty retail chains interviewed eight store operations managers about in-store returns of online orders. The three people who observed the calls have about 120 observations between them, and one empty wall.

1. Write one observation per note

Each person writes down anything relevant from their notes, one observation per note. GOV.UK's advice is to use a single color at this stage and write exactly what you saw or heard, such as a quote or a behavior, not what you think it means. Check recordings for exact wording where you can.

Tag every note with the participant's ID, such as "P3". You will need it in step 3. How to take customer interview notes covers keeping what people said separate from your interpretation.

Write thisNot this
P3: "If the receipt is on their phone, I have to call the online team to find the order."P3's store has a bad process for online returns.
P5 keeps a paper log of online returns to reconcile at month end.Stores need better reporting.
P1: online orders can't be refunded at the register; the customer waits for head office.Refund delays frustrate customers.

The right-hand column holds conclusions. They may be correct, but they belong in step 3.

2. Sort silently, with no categories decided in advance

Put all the notes on a wall or digital whiteboard in no order, and have everyone move related ones together. ASQ recommends sorting silently at first, without deciding categories in advance, and lets anyone move a note someone else placed. A note that fits nowhere can stay on its own, and one that belongs in two groups can be copied.

People will disagree about where notes belong (that is the useful part). NN/g suggests grouping by content before naming groups, and warns against forcing notes into clusters and against dismissing small clusters, which can hold a view only a few participants raised.

GOV.UK lists common ways groups form: by topic, by stage in a process, by step in a transaction or by type of user. In the returns example, the first groups might be "finding the online order", "issuing the refund", "what happens to the item" and "month-end reconciliation".

3. Name the groups, then write findings with participant IDs

Once the groups settle, title each one. ASQ suggests using a note that captures the group's meaning as the header, or writing a new one. GOV.UK suggests splitting large groups into smaller themes where the notes allow.

Then GOV.UK recommends writing each finding as a short statement on a different color note:

  • Finding: Store staff can't look up an online order without the customer's email or a call to the online team. (P1, P2, P3, P6, P8)
  • Finding: Some stores keep their own paper or spreadsheet logs of online returns to reconcile later. (P5, P7)

List the participant IDs behind every finding, because a cluster of 15 notes might come from one talkative person. As how to analyze customer interviews puts it, ten comments from one person still represent one person's experience. Here, the first finding rests on five of the eight managers and the second on two.

4. Agree a few actions and who owns them

GOV.UK suggests a third color for actions, such as design ideas, new questions for the next round, prototype changes or items for the product backlog. NN/g suggests prioritizing the clusters that matter most, using dot voting if discussion stalls, and nominating a point person to see the actions through.

For the returns startup, actions might be:

  • Test whether staff can find an online order by phone number or card.
  • Ask the next round of interviewees how they reconcile online returns.
  • Interview someone on a retailer's online team, whose side of the process nobody has heard yet.

Photograph or export the map and write a short summary. How to turn customer interviews into a testable product decision and running a readout with skeptical stakeholders cover what to do with it next.

Paper and tape still work

You don't need software. Richard Krueger's 2002 guide to focus groups does the same with printed transcripts: cut out quotes, tape them to a large sheet for each question, mark each quote's source with a color or code, then write a paragraph summarizing each sheet (Krueger, University of Minnesota). Krueger's advice to take a break and look at the big picture before writing up applies to any affinity map.

Three ways an affinity map goes wrong

  • Counting notes instead of people. Check how many participants support each finding.
  • Stopping at the clusters. Labeled groups aren't findings. Finish with statements and actions.
  • Unmarked participant types. If you interviewed store managers and head-office staff, each note should show which.

Book the session while the interviews are fresh

Within a day or two of your last interview, book a session with everyone who observed, allowing about an hour for every two hours of interviews. Ask each person to bring observations one per note, tagged with participant IDs. Sort silently for the first 15 minutes, then name the groups, write findings with the IDs behind them, and agree on no more than three actions.

If the map shows a role nobody has interviewed yet, that is your next recruit. Instant Expert can find people who match a description you write, such as "store operations managers at specialty retail chains". You review who it finds, it sends your invitations, and you pay only for calls that get booked. The operations professionals in retail directory page is one place to start.

Affinity mapping in four passes

  1. 1

    Extract

    Write one observation per note in a single color, quoting or describing behavior, tagged with a participant ID.

  2. 2

    Sort

    Group related notes silently at first, with no categories decided in advance.

  3. 3

    Name and conclude

    Title each group, then write findings on a second color with the participant IDs behind them.

  4. 4

    Act

    Agree a few actions on a third color and name who owns each one.

Observations, findings and actions go on different colored notes, so the evidence stays separate from what you concluded from it.