Loading content
An affinity diagram is a structured facilitation method for grouping and synthesizing qualitative ideas, observations, or requirements. Teams use it in workshops to reveal patterns, form hypotheses, and clarify priorities. It fosters shared sense-making and supports early-stage decision making in product discovery.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
An affinity diagram is a structured facilitation method that groups qualitative ideas, observations, or requirements into themes so a team can surface patterns and derive review and next steps.
According to Wikipedia, the term “affinity diagram” was devised by Jiro Kawakita in the 1960s and is sometimes referred to as the “KJ Method.” The same source describes its use to sort large numbers of ideas—often stemming from brainstorming—into groups based on “natural relationships” for review and analysis, and to organize notes and insights from “contextual inquiry” (field interviews).
Imagine a sorting board that turns many single items into a coherent structure step by step: (1) participants write ideas/observations on cards or sticky notes and pin them initially without categories. (2) the team looks for content connections and moves items until related ones form clusters. (3) if clusters become too large, you split them into subgroups so each theme stays manageable. (4) then the team assigns clear labels to the clusters. (5) finally, the team prioritizes the most important clusters to set the focus for the next steps.
Single statements captured separately (e.g., one observation, one design-idea element, or one requirement) that are clustered later.
Clusters form because items are content-connected; the team recognizes the tie through recurring aspects, similar problems/ideas, or shared functionality.
Grouping is iterative until all items are placed; large clusters are split into subgroups to expose differences within a theme.
A label compresses a cluster into a reusable term so the team can reference it consistently later.
Here, prioritization means choosing which clusters matter most for the next work and decisions, setting the next focus in the project.
Affinity diagrams are useful when a team has a lot of unstructured qualitative input in early project or discovery phases (for example, outputs from brainstorming or notes and insights from field interviews) and needs a shared set of themes. They work particularly well when multiple perspectives can collaborate during the workshop sorting. Limits: outcomes depend on how the team interprets relationships between statements, and the method requires time for deep engagement and discussion. For questions that require statistically grounded distributions or measurement evidence, an affinity diagram does not replace that kind of validation.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.