What is an affinity map in UX?
An affinity map in UX is a visual grouping of research notes, quotes and observations into themes so patterns across many users become easy to see.
also calledaffinity diagram · affinity diagramming · KJ method
After a week of interviews you usually own a few hundred scraps of information and no idea what they add up to. An affinity map is how you turn that pile into a handful of clear themes. You write each observation on its own note, stick the notes on a wall, and slowly drag similar ones next to each other until the clusters start talking back.
- An affinity map groups raw research notes into themes so patterns appear.
- One observation per note, and let the groups emerge before you name them.
- Name clusters by the insight they hold, not just by the topic.
- It shows patterns in qualitative data, but it does not tell you how many users are affected.
What goes on the wall
Each note holds exactly one thing: a quote from a participant, something you saw them do, a pain point, a surprise. Short and specific beats clever. "Skipped the tutorial and then got lost on step three" is useful. "Onboarding issues" is a label, not an observation.
The notes come straight from your raw material, such as interview transcripts, usability test recordings, support tickets or survey comments. You are not summarizing yet. You are just getting everything onto a surface where you can move it around.
Physical sticky notes on a real wall still work beautifully, mostly because people physically cannot hide behind a laptop. Digital whiteboards do the same job when the team is remote.
How to build one, step by step
The process is simple, and the trick is to resist the urge to name things too early.
- Write one observation per note, using the participant's own words where you can.
- Put all the notes up in no particular order and read them as a team.
- Silently move notes that feel related next to each other. Talking comes later, so nobody's loud opinion steers the groups.
- When a cluster settles, give it a name that describes the theme, ideally as a sentence rather than a single word.
- Look for bigger groupings: several clusters may belong under one umbrella insight.
- Pick the themes that matter most and turn them into design decisions or next research questions.
Expect the first pass to be messy. Notes will move three or four times before they settle.
Why teams like it
The biggest benefit is that the structure comes from the data, not from your assumptions. If you start with categories in your head, you tend to find evidence for them. When groups emerge from the notes, you sometimes discover themes you did not expect, like the fact that half your frustrated users are really confused about pricing, not about the interface.
It also gets everyone into the same room with the same evidence. Stakeholders who watch a cluster of twelve similar quotes grow on the wall tend to believe it more than one researcher saying "people found this confusing".
Finally, it makes patterns visible. A single complaint is an anecdote. Eleven notes in one cluster is something you cannot ignore.
Common mistakes
The usual one is grouping by topic instead of by meaning. A cluster named "checkout" tells you where the problem is but not what it is. Push yourself to name clusters by the insight, such as "People are unsure whether their card was charged".
Another trap is sorting your notes into the categories you already planned to find. If the groups look exactly like your slide outline, you probably forced them.
Teams also forget to keep the connection to the source. Mark each note with a participant code so that when someone asks "who said that?" you can answer, and so you can see whether a cluster comes from one loud participant or from many.
When it fits and when it does not
Use it after qualitative research, when you have more raw notes than you can hold in your head. It is especially handy for interview studies, diary studies and open-ended survey answers.
Skip it when you only have a few data points, since you can just read them. It also is not a replacement for numbers. If you need to know how many users hit a problem, pair it with quantitative data, because a big cluster of notes reflects how much you wrote down, not necessarily how common the issue is.
Affinity map: your questions, answered
What is an affinity map used for in UX?
It is used to make sense of large amounts of qualitative research, such as interview notes or open survey answers. By grouping similar observations into themes, a team can see which problems and needs come up most and decide what to design or study next.
How do you make an affinity map?
Write each observation on a separate note, put them all on a wall or digital board, and group notes that feel related without talking at first. Then name each cluster with an insight, look for larger themes, and decide which ones to act on.
What is the difference between an affinity map and an empathy map?
An affinity map organizes many people's research notes into themes, while an empathy map describes what one user or persona says, thinks, does and feels. Teams often build an affinity map first and use its themes to fill in an empathy map.
How many notes should an affinity map have?
There is no fixed number. A small study might produce fifty notes and a large one several hundred. What matters is that every note holds one clear observation. If the wall gets too crowded to read, group the studies and work in stages.
Can you do affinity mapping remotely?
Yes. Digital whiteboard tools let a distributed team add, move and cluster virtual sticky notes together in real time. Remote sessions work best with a clear facilitator and a short silent grouping phase, so one person does not take over the clusters.
More quick answers
Who invented the affinity diagram?
The method is usually credited to Japanese anthropologist Jiro Kawakita in the 1960s, which is why it is sometimes called the KJ method.
Is affinity mapping qualitative or quantitative?
It is a qualitative technique. It organizes words and observations rather than numbers, so use it to find themes, not to measure how common a problem is.
What is the difference between affinity mapping and card sorting?
In affinity mapping the research team groups its own notes. In card sorting, the users group items and show you how they expect content to be organized.
What tools can I use for affinity mapping?
Sticky notes on a wall are the classic choice. For remote teams, any shared whiteboard or design tool with movable notes will do the job.
How long does an affinity mapping session take?
A focused session on a small study can take one to two hours. Bigger research rounds often need a half day, mostly to write the notes and agree on cluster names.
An empathy map in UX is a simple one-page diagram that captures what a user says, thinks, does and feels, to help a team see the world from their side.
Qualitative user research is the study of people's behavior, needs and motivations through observation and conversation, to learn why they act as they do.
A user interview in UX is a one-on-one conversation where a researcher asks people about their goals, habits and frustrations to understand their real needs.
A persona in UX is a fictional but research-based profile of a typical user, describing their goals, habits and frustrations to keep design decisions grounded.
Card sorting in UX is a research method where people group labeled cards into categories, showing how they expect content to be organized.
Found this useful? A GitHub star helps other designers find it.