View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Affinity Diagramming |  Agile Example Mapping |  Operations Root Cause Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45–90 min | 30-60 min | 1-4 h | 15-30 min |
Participantsdifferent | 3-10 | 3-7 | 3-8 | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Example Map, Acceptance Criteria, Open Questions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | SynthesisQualitativeRoot cause | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Root causeProblem solvingQualityIncident | Root causeIncidentLeanProblem solving |