The Affinity Diagram: The 10-Minute Tool That Tames Your Messiest Brainstorm

When a project begins with dozens of complaints, observations, ideas and assumptions, the first challenge is not finding a solution. It is finding structure.

This is where the Affinity Diagram becomes valuable. The tool organises large volumes of ideas into meaningful categories based on natural relationships, allowing a project team to see patterns that are difficult to identify in an unstructured brainstorm.

In the realm of DMAIC, the Affinity Diagram is especially useful during the Define phase. It helps teams interpret Voice of the Customer (VOC) data, identify themes, clarify project boundaries and develop a focused problem statement.

The result is a practical transition from:

“We have a lot of customer complaints.”

to:

“Customers are experiencing delays primarily related to order entry, warehouse preparation and delivery coordination.”

That shift creates a stronger foundation for Measure and Analyse.

What Is an Affinity Diagram?

An Affinity Diagram, sometimes called the KJ method, is a visual tool for sorting a large number of ideas, statements or data points into groups according to their natural relationships.

Unlike a traditional brainstorm that may produce a long list, an Affinity Diagram helps answer three questions:

1. Which ideas appear to be connected?
2. What common theme describes each group?
3. Which themes deserve further investigation?

The tool does not prove causation. It does not identify the statistically significant root cause. Its purpose is to organise qualitative information so the team can decide what to measure next.

Typical inputs include:

• Customer survey comments
• Complaint records
• Interview notes
• Employee observations
• Workshop ideas
• Product returns
• Service feedback
• Process concerns
• Improvement suggestions

Each idea is usually written on a separate sticky note or digital card. The notes are then grouped into clusters based on meaning rather than department, seniority or personal preference.

Why Use It in the Define Phase of DMAIC?

The fundamental purpose of the Define phase is to establish a clear improvement opportunity. This includes identifying the customer, understanding the business need, defining the process and agreeing on the problem to be addressed.

An Affinity Diagram supports this work by turning unstructured VOC into themes that can become measurable requirements.

A typical Define-phase sequence looks like this:

1. Collect Voice of the Customer data.
2. Write each customer statement separately.
3. Group statements according to natural relationships.
4. Name each group with a concise header.
5. Convert the themes into CTQs or measurable requirements.
6. Use the evidence to develop the problem statement.
7. Confirm scope, stakeholders and project objectives.

For example, customer statements such as:

• “My order arrived two days late.”
• “The tracking information was not updated.”
• “The delivery window was unclear.”
• “The item was packed incorrectly.”
• “I received the wrong product.”

may initially appear to be separate problems. Once grouped, they could reveal broader themes such as:

• Delivery reliability
• Information visibility
• Order accuracy
• Packaging quality

These themes guide the next stage of investigation without prematurely prescribing a solution.

A 40-Note Project Kickoff Example

Consider a hypothetical logistics company experiencing declining customer satisfaction. During the project kickoff, the team reviews recent VOC data from customer surveys, support tickets and delivery complaints.

The team writes 44 individual statements on sticky notes. Examples include:

• “The parcel arrived after the promised date.”
• “The tracking page showed no movement for three days.”
• “The driver could not locate the delivery address.”
• “The package was damaged at the corner.”
• “The invoice did not match the order.”
• “Customer support transferred me three times.”
• “The delivery window was too broad.”
• “The replacement order took longer than the original.”
• “The product was packed with the wrong accessories.”
• “I received no notification when the parcel left the warehouse.”

Rather than immediately voting on the most common complaint, the team silently arranges the notes on a large wall. Similar ideas are placed together. The group discusses only those notes that appear ambiguous or could reasonably belong to more than one cluster.

After approximately 10 minutes, five themes emerge:

1. Delivery Timeliness : 13 notes

This group includes late deliveries, missed delivery windows and replacement orders that take too long.

2. Tracking and Communication : 9 notes

These notes relate to missing notifications, inaccurate tracking and unclear delivery information.

3. Order Accuracy : 8 notes

This group includes incorrect products, missing accessories and invoice mismatches.

4. Packaging and Handling : 7 notes

These statements describe damaged parcels, inadequate protection and unsuitable packaging.

5. Support and Resolution : 7 notes

These notes concern repeated transfers, slow responses and inconsistent resolution of problems.

The Affinity Diagram has not yet identified the root cause. However, it has transformed 44 disconnected observations into five practical investigation areas.

That is a significant improvement in clarity.

The team can now ask more precise questions:

• What percentage of deliveries miss the promised date?
• At which process step is tracking information delayed?
• How often do order-entry errors cause incorrect shipments?
• Which packaging conditions correlate with transit damage?
• What is the average time from complaint to resolution?

These questions lead naturally into Measure.

From VOC Themes to CTQs

Voice of the Customer expresses what customers want, expect or experience. Lean Six Sigma teams must translate that feedback into measurable requirements known as Critical to Quality characteristics, or CTQs.

The Affinity Diagram provides a useful bridge.

This translation is essential because a theme such as “better communication” is too broad to manage. A CTQ such as “95% of tracking updates posted within 30 minutes of the relevant scan” is measurable and testable.

You can support this Define-phase work with the VOC Priority Matrix Calculator and the Critical to Quality Tree Calculator.

Developing a Strong Problem Statement

A problem statement should describe the current gap without embedding a preferred cause or solution. It should be specific enough to guide the project while remaining open to evidence from Measure and Analyse.

A reliable problem statement usually includes:

• What is happening
• Where it is happening
• When it is happening
• How large the gap is
• Who is affected
• Why the gap matters

Using the logistics example, a weak statement might be:

“Our delivery system needs better software and more warehouse staff.”

This is not a strong problem statement because it assumes both the cause and the solution.

A stronger version would be:

“Between January and June 2026, 18.4% of standard customer orders were delivered after the promised date, compared with the service target of 95% on-time delivery. The gap affects domestic e-commerce customers and has contributed to a 22% increase in delivery-related support contacts.”

This statement is:

• Data-based
• Time-bound
• Customer-focused
• Solution-neutral
• Suitable for a DMAIC project charter

Another example from the order accuracy theme is:

“During Q2 2026, 3.8% of outbound orders contained an incorrect or missing item, resulting in rework, replacement shipments and customer complaints. The current performance does not meet the requirement of at least 99% first-pass order accuracy.”

These are useful good problem statement examples because they define the gap without claiming to know its root cause.

To test the clarity of your wording, use the Problem Statement Clarity Calculator.

How to Run an Affinity Diagram Effectively

Use the following protocol for a focused workshop.

1. Define the focus question

Start with a neutral question that frames the discussion.

Examples include:

• “What prevents customers from receiving orders on time?”
• “What factors contribute to delays in patient admissions?”
• “What are the main barriers to accurate invoice processing?”
• “What prevents employees from completing the approval process efficiently?”

A good focus question is broad enough to invite insight but narrow enough to support a defined project.

2. Gather the data

Use existing VOC data wherever possible. Combine customer comments with interviews, complaint codes and operational observations.

Avoid rewriting statements so heavily that their original meaning disappears. The customer’s language often reveals expectations that internal terminology conceals.

3. Write one idea per note

Each sticky note should contain one clear thought. Combining several concerns on one note makes grouping more difficult.

For example:

• “The parcel was late and the tracking was inaccurate” should become two notes.
• “The invoice was incorrect” should remain one note unless the data distinguishes price, quantity and product errors.

4. Group by natural relationship

Ask participants to work silently at first. Silence reduces the risk that the most senior or most vocal person will determine every category.

Place notes together when they express a similar need, experience or process condition. Do not group them merely because they originate from the same department.

5. Name each cluster

Write a short, descriptive header above each group. Strong headers capture the shared concept without becoming overly detailed.

Examples include:

• Order accuracy
• Response speed
• Process visibility
• Product availability
• Handover quality

6. Validate the themes

Review each cluster with the team and ask:

• Does every note belong here?
• Is the header specific enough?
• Are two clusters expressing the same concept?
• Is any important data missing?
• Does this theme matter to the customer or business?

The final diagram should reflect shared understanding, not forced agreement.

Common Mistakes to Avoid

An Affinity Diagram is straightforward, but facilitation quality determines its value. Avoid these common errors:

• Starting with solutions: “Implement a new system” is not a customer observation.
• Grouping by organisational chart: Departments are not necessarily process themes.
• Allowing one person to dominate: Use silent sorting before discussion.
• Treating frequency as causation: A frequently mentioned issue may still require further analysis.
• Using vague headers: “Other,” “process issues” and “communication” often require refinement.
• Skipping measurement: Themes are hypotheses until data confirms their size and impact.
• Writing a solution into the problem statement: Preserve flexibility for the Analyse phase.

The Affinity Diagram is a sense-making tool. Its power lies in helping teams move from complexity to a structured set of questions.

Turn Better Grouping into Better Improvement

A well-run Affinity Diagram can shorten the path from customer feedback to project clarity. In less than 10 minutes, a team may organise dozens of ideas into a manageable set of themes, identify candidate CTQs and create the raw material for a credible problem statement.

The tool is simple, but it supports sophisticated Lean Six Sigma thinking:

• VOC captures customer expectations.
• Affinity grouping reveals natural relationships.
• CTQs convert expectations into measures.
• Problem statements define the performance gap.
• DMAIC provides the disciplined path to investigate and improve it.

If you want to build these skills into complete project capability, explore Lean Six Sigma Green Belt Online Training. The course develops practical knowledge across project charters, VOC, SIPOC, data collection, root-cause identification, statistical analysis, improvement pilots and control planning.

You can also review the Define Phase Calculators to structure your project selection, customer requirements, scope and problem statement before moving into Measure.

Use an Affinity Diagram in your next Define workshop, translate the themes into measurable CTQs, and pursue accredited Lean Six Sigma training or certification to lead improvement projects with confidence.

Kaizen. Kai-Care. Kai-Done. ( Lean Six Sigma)