All posts
Allen
Author, Content Operations Manager·Originally published Jan 26, 2026 · Updated Nov 14, 2026
Cover reading Affinity Diagram, steps, a worked example, PMP and how it differs from a mind map, with scattered yellow sticky notes sorted into four groups under header cards

Affinity Diagram: Steps, Example, PMP & vs Mind Map

What changed (Nov 14, 2026): Rewrote the guide around the method: definition, KJ method origin (ASQ, Scupin 1997), when to use it, five steps, a worked 20-note example with figures, a free template (PNG and CSV), a PMP section based on the PMBOK Guide Sixth Edition and the July 2026 exam outline, a mind map comparison, common mistakes from NN/g, nine FAQs and sources. Replaced the two dead PMI and ASQ links, corrected competitor claims (Miro includes Docs on the free plan, Mural has a free plan, Lucidspark is Lucid's whiteboard), removed superiority and compliance claims about AFFiNE, added a disclosure and noted that AFFiNE AI is a paid add-on.

Short answer: An affinity diagram, also called affinity mapping or the KJ method, is a way to sort a large pile of ideas, observations or requirements into groups of related items, then name each group so the team can see the themes. You write one idea per sticky note, sort the notes in silence, give each group a header card, and decide which groups matter most. Project managers use it to make sense of stakeholder requirements; UX researchers use it to turn interview notes into findings.

Updated November 14, 2026. Disclosure: AFFiNE publishes this blog and makes a docs-and-whiteboard app that can be used for affinity diagrams. The method below works on paper or in any whiteboard tool. The worked example, figures and template were made by us; the example data is fictional.

Five steps of an affinity diagram shown as five panels: write a focus question, write one idea per note, sort the notes in silence, name each group with a header card, then add supergroups and dot votes to pick next steps

What is an affinity diagram?

An affinity diagram organizes a large number of ideas into their natural relationships. ASQ describes it as the organized output of a brainstorming session and lists its other names: affinity chart, affinity mapping, K-J Method and thematic analysis. Nielsen Norman Group defines affinity diagramming as organizing related observations, ideas, concepts or findings into distinct clusters, and notes that UX teams also call it collaborative sorting or snowballing.

The key point is the direction of work. You do not start with categories and fill them. You start with the raw items and let the groups emerge from what the items say. That is why the method is useful when a team has "too much information and no structure yet," and why it is a poor fit when the categories are already known.

An affinity diagram has four parts:

PartWhat it isIn the example below
NotesOne idea, fact or quote per sticky note, ideally 3 to 7 words"Payment date is never shown"
GroupsNotes the team placed side by side because they belong togetherFour notes about claim status
Header cardsA short label that states what the group means"People can't tell when they'll be paid"
Supergroups (optional)Related groups combined under a broader heading"Get paid without chasing anyone"

Where the KJ method comes from

The method is named after Japanese anthropologist Jiro Kawakita (Kawakita Jiro), whose initials give "KJ." ASQ dates its creation to the 1960s. Kawakita developed it while struggling to interpret ethnographic field data from Nepal, and he described the approach in his 1967 book Hassōhō ("abduction method"), according to anthropologist Raymond Scupin's paper The KJ Method: A Technique for Analyzing Data Derived from Japanese Ethnology (Human Organization, 1997). Scupin also notes that the method spread through Japanese management and education.

In 1976 the Union of Japanese Scientists and Engineers (JUSE) included the affinity diagram in its seven new quality control tools, also called the seven management and planning tools. That is why quality teams treat it alongside the interrelationship diagram and tree diagram, and why it often comes before a fishbone diagram in root cause work.

When to use an affinity diagram

ASQ suggests it when you face many facts or ideas in apparent chaos, when an issue seems too large and complex to grasp, and when the group needs consensus. Typical uses:

  • Requirements: sorting dozens of stakeholder requests from interviews or workshops before writing a business requirements document.
  • UX research synthesis: turning interview notes, usability observations or survey comments into findings.
  • Retrospectives and lessons learned: grouping what went well and what did not.
  • Quality and root cause work: grouping symptoms and suspected causes before deeper analysis.
  • Open-ended survey answers: finding themes in free-text responses.

Use something else when:

  • You have only a handful of items. A simple list or discussion is faster.
  • The categories are fixed in advance, for example sorting support tickets into existing queues. That is classification, not affinity diagramming.
  • You need to explore one known topic outward. That is a mind map (see the comparison below).
  • You need to choose between options. Use a decision matrix or an impact effort matrix after the themes are clear.

How to make an affinity diagram in 5 steps

These steps combine the ASQ procedure with the three-step version Nielsen Norman Group uses in UX workshops (generate notes, cluster them, prioritize clusters).

Step 1: Write a focus question

Write one question at the top of the board, such as "What slows people down when they claim expenses?" NN/g lists a missing focus question as the first common pitfall: the same notes can be grouped in several valid ways, and the question decides which grouping is useful.

Step 2: Put one idea on each note

Each note holds a single idea, observation or quote. ASQ suggests 3 to 7 words and a marker that can be read from a distance. For research notes, add a source code (P1, P2) so you can trace every finding back to a participant. Spread the notes out randomly so everyone can see them. ASQ says affinity diagrams usually have 40 to 60 items, and 100 to 200 is not unusual.

Step 3: Sort the notes in silence

Everyone moves notes at the same time, placing related notes side by side. In ASQ's procedure nobody talks during this step, and you do not decide categories or headings in advance. If someone moves a note you placed, move it back or make a copy, and let the disagreement surface in step 4. A few notes may stay on their own; that is fine.

Step 4: Discuss and name each group

Now talk. For each group, agree on a header card that captures what the notes have in common. A good header card states the insight ("Claims wait on one busy approver") rather than a one-word topic ("Approvals"), so a reader who never saw the notes still understands the finding.

Step 5: Build supergroups, vote and choose next steps

Combine related groups under supergroups if it helps (ASQ step 4). Then prioritize. NN/g recommends ending with clear priorities and next steps; dot voting is a common way to do it. Record who owns each next step before the session ends.

Affinity diagram example: 20 interview notes

Here is a complete, fictional example. A product team interviewed eight employees (P1 to P8) about their company's expense app and wrote one finding per note.

Affinity diagram example before sorting: twenty yellow sticky notes with interview findings about an expense app, such as receipt photo comes out blurry and payment date is never shown, each marked with a note number and participant code

After silent sorting and discussion, the 20 notes formed five groups:

Header cardNotesVotes
Capturing receipts takes too many triesReceipt photo comes out blurry; Retyped totals the app misread; Lost paper receipts before submitting; Hotel bill has too many lines; Wants to forward email receipts7
People can't tell when they'll be paidCan't see where my claim is; Emailed finance twice about status; Payment date is never shown; Surprised by a partial payout6
Claims wait on one busy approverManager approves only on Fridays; No reminder reaches the approver; Approval stuck while manager travels; Two approvals needed above $5005
The rules are hard to find before submittingUnsure which meals are covered; Mileage rate is hard to find; Rejected for missing project code; Policy PDF is 40 pages long4
Long claims break on mobileSubmitting on phone times out; Can't save a half-done claim; Uses laptop for long trips instead2

The team then added two supergroups: Get the claim right the first time (receipts, rules, mobile) and Get paid without chasing anyone (approver, payment status). Eight people had three dots each.

Affinity diagram example after sorting: the twenty notes arranged in five colored groups under dark header cards, with two dashed supergroups labeled get the claim right the first time and get paid without chasing anyone, and red vote dots above each group

What the team decided: the two highest-voted groups, receipt capture (7) and payment status (6), became problem statements for the next sprint. The approver group (5) went to the finance lead, because the fix was a policy change, not a product change. Notice that no single note said "status visibility is a problem"; the theme only appeared once four separate complaints sat together.

Free affinity diagram template

Download, print or drop these onto any whiteboard. No sign-up needed.

Blank affinity diagram template with lines for the focus question and team, a dashed area for unsorted notes, two supergroup panels each holding three header cards with five vote circles and four empty note slots, and a next steps line at the bottom

Affinity diagrams for the PMP exam

In the PMBOK Guide, Sixth Edition, affinity diagrams appear as a tool of process 5.2 Collect Requirements, under "data representation" alongside mind mapping. Nominal group technique sits in the same process under "interpersonal and team skills," and brainstorming under "data gathering." You can see the full tools-and-techniques list in PMI's PMBOK Guide Sixth Edition errata (Figure 5-4).

The PMP exam itself is not organized by PMBOK processes. PMI updated the exam in July 2026; the 2026 Exam Content Outline weights People 33%, Process 41% and Business Environment 26%, and uses scenario-based questions. Its process tasks include "Develop and manage project scope" and "Collect and analyze data to make informed project decisions." So expect a situation ("stakeholders generated 150 ideas, what next?") rather than a definition. PMI also says core principles have not changed, so older study material on these tools still applies.

How to tell the four techniques apart:

TechniqueWhat it doesClue in a question
BrainstormingGenerates many ideas quickly, without judging them"The team needs as many ideas as possible"
Affinity diagramSorts a large number of ideas into groups for review and analysis"Hundreds of ideas need to be organized or classified"
Mind mappingConsolidates ideas from individual brainstorming into one map, showing common ground and differences, and can spark new ideas"Combine everyone's ideas around one topic"
Nominal group techniqueAdds a structured round of voting or ranking so the group can prioritize ideas"Rank the ideas; make sure quieter members have an equal say"

Practice questions

These are our own practice questions, not official PMI items.

1. A requirements workshop for a new HR portal ends with about 150 stakeholder ideas on sticky notes. The project manager wants the team to organize them into related groups before writing the requirements documentation. What should the project manager use?

A. Mind mapping B. Affinity diagram C. Nominal group technique D. Context diagram

Answer: B. The task is to classify a large number of existing ideas into groups. Mind mapping builds outward from one topic; nominal group technique ranks ideas; a context diagram shows how a system interacts with users and other systems.

2. The ideas from question 1 have been grouped and named. The sponsor now wants the requirements ranked, and the project manager is worried that two senior managers will dominate the discussion. What is the best next step?

A. Ask the senior managers to rank the groups B. Run a nominal group technique session C. Redo the affinity diagram D. Add the groups to the risk register

Answer: B. Nominal group technique gives each participant an equal, structured vote, which addresses both the ranking and the dominance concern.

Affinity diagram vs mind map

This is the comparison most people search for, and it comes up in PMP prep and UX courses alike.

Mind map vs affinity diagram: on the left a mind map grows from a central team offsite topic to six branches; on the right scattered yellow notes are sorted into three themed groups under header cards, with a summary of starting point, direction and use for each
Mind mapAffinity diagram
Starting pointOne central topic you already knowMany facts or ideas you have not organized yet
DirectionTop-down, divergent: one idea branches into manyBottom-up, convergent: many ideas become a few themes
StructureA tree of branches and sub-branchesGroups under header cards, optionally supergroups
Usually done byOne person or a groupBest as a group, to build shared understanding
Good forPlanning, outlining, breaking down a project, studyingResearch synthesis, requirements, retrospectives, finding patterns
In PMBOK 6, Collect RequirementsData representationData representation

The two work well in sequence. Use an affinity diagram to find the themes in what you collected, then put one theme at the center of a mind map to plan what to do about it. For layouts, see these mind map examples.

Common affinity diagram mistakes

  • No focus question. NN/g's first pitfall: without a question, the team argues about which grouping is "right" when several are valid.
  • Grouping by keyword. NN/g's second pitfall: putting every note that mentions "app" together, instead of grouping by what the notes mean. In the example, "Hotel bill has too many lines" and "Receipt photo comes out blurry" share no words but describe the same problem.
  • Groupthink. NN/g's third pitfall. Silent sorting, sorting before discussion, and anonymous dot voting all reduce it.
  • Notes that hold several ideas. A note like "Receipts are blurry and approvals are slow" cannot go in one group. Split it.
  • Categories decided in advance. If the header cards exist before the notes are sorted, you are filling buckets, not finding themes.
  • One-word header cards. "Mobile" says little; "Long claims break on mobile" tells the reader what was found.
  • Forcing every note into a group. A lone note can be a real outlier. Keep it visible.
  • No next step. End with priorities and owners, or the board becomes a photo nobody opens again.

Affinity diagram tools

You do not need software. Sticky notes, markers and a wall are still what ASQ's procedure assumes. A digital board helps when the team is remote, when you have more notes than wall space, or when you need a record. Look for: fast sticky-note entry, free movement on a large canvas, a way to group or frame notes, voting, and an export or link you can share.

Details below were checked on November 13 and 14, 2026, on each vendor's pricing and help pages. Plans change, so confirm before you buy.

OptionFree planHelp with groupingGood fit
Paper sticky notes and a wallNot applicableNone; people do the sortingIn-person workshops; the original method
Miro3 editable boards; Docs, Tables and Slides on the canvas. Starter from $8 per member per month, billed yearlyClustering by color, tag, author, and AI-powered keyword or sentiment clusteringLarge remote workshops and client boards
Mural3 editable murals. Team+ $9.99 per month billed annually, or $12 monthlyFacilitation features such as a timer, voting sessions and private modeFacilitated workshops
FigJamStarter plan: 3 FigJam files in the team folder, plus unlimited drafts (Figma help)AI sort stickies by topic, color, author or stamps, on paid plansDesign teams already using Figma
Lucidspark3 editable boards. Individual from $9 per monthSort by tag, color or votes into containers; Lucid's pricing page lists tags and assisted grouping as paid-plan featuresTeams that also use Lucidchart
AFFiNE (our product)Unlimited local workspaces; free Cloud with 10 GB and up to 3 members per workspaceManual grouping with groups and frames; optional paid AI add-onKeeping the board and the written synthesis in one place

Miro, Lucidspark and FigJam have the most built-in sorting help. If your board will hold hundreds of notes from a large remote group, start there. Any of these tools is fine for 20 to 60 notes. For more options, see our comparison of online whiteboard tools.

Making an affinity diagram in AFFiNE

We make AFFiNE, so weigh this section accordingly. AFFiNE's Edgeless mode is a whiteboard on the same document as a page, which is useful when the affinity diagram should turn into a written report or requirements list without copying it into another app.

  1. Create a doc, switch to Edgeless, and put the focus question at the top.
  2. Add one sticky note per idea. If your notes are in a list, paste them in rather than retyping.
  3. Drag related notes next to each other, then select each cluster and group it, or draw a frame around it and name the frame as the header card.
  4. Use connectors to show how groups relate, and a larger frame for each supergroup.
  5. Switch to Page mode in the same doc to write up the findings and next steps next to the board.

Limits to know: we did not find a one-click cluster-by-tag or cluster-by-color command like Miro's or Lucidspark's in AFFiNE's documentation, so sorting is manual. Free Cloud workspaces allow up to 3 members, which suits a small team rather than a large workshop. AFFiNE AI can summarize or suggest themes for selected text, but it is a paid add-on ($8.9 per month billed annually, with 10 free trial uses) and it runs through AFFiNE Cloud, so you need to sign in. If you prefer to start from a layout, the design thinking template includes space for this kind of synthesis.

Frequently asked questions

What is an affinity diagram in project management?

It is a technique for sorting a large number of ideas, usually stakeholder requirements, into related groups so the team can review and analyze them. In the PMBOK Guide, Sixth Edition, it is listed as a data representation tool in the Collect Requirements process, next to mind mapping.

Is an affinity diagram the same as affinity mapping?

Yes. Affinity diagram, affinity map, affinity mapping, affinity chart and the KJ method all describe the same technique. UX teams tend to say "affinity mapping"; quality and project management sources tend to say "affinity diagram."

What is the difference between an affinity diagram and a mind map?

A mind map starts from one known topic and branches outward (top-down, divergent). An affinity diagram starts from many scattered ideas and groups them into themes (bottom-up, convergent). Use a mind map to plan or break something down; use an affinity diagram to make sense of what you collected.

Is the affinity diagram on the PMP exam?

It can be. The PMBOK Guide Sixth Edition lists it under Collect Requirements, and prep courses still cover it. The July 2026 PMP exam is built on the 2026 Exam Content Outline and uses scenario questions, so you are more likely to be asked when to use it than to define it.

What is the KJ method?

The KJ method is the original name of the affinity diagram, from the initials of Japanese anthropologist Jiro Kawakita, who developed it in the 1960s to make sense of field research data. Its core is letting groups emerge from the data, then naming them.

How many people do you need for affinity diagramming?

You can do it alone, but it works best as a group because the discussion builds shared understanding. A group small enough that everyone can reach the board, often three to eight people, keeps silent sorting manageable. Larger groups can split the notes, sort in parallel, then merge.

How many sticky notes does an affinity diagram need?

There is no fixed number. ASQ says affinity diagrams tend to have 40 to 60 items and that 100 to 200 is not unusual. Below about 15 to 20 notes, a simple list is usually enough.

What are the best tools for creating affinity diagrams?

For in-person sessions, paper sticky notes and a wall. For remote work, Miro, Mural, FigJam and Lucidspark all have free plans and sticky-note sorting features; Miro and Lucidspark can cluster notes by tag or color. AFFiNE is an option when you want the board and the written synthesis in one document.

Is there a free affinity diagram template?

Yes. This page has a free blank template as a printable PNG, a filled example and a CSV worksheet. You can also use a blank board in any whiteboard tool: put the focus question at the top and leave an area for unsorted notes.

Sources

Checked November 13 and 14, 2026: