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 |  Operations 8D Problem Solving |  Domain Modeling Domain Context Map |  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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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 | High | Medium | Low |
Timedifferent | 45–90 min | 1-6 Wochen | 1-3 h | 15-30 min |
Participantsdifferent | 3-10 | 4-10 | 3-10 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Domain Context Map, Boundary Notes, Ownership Map | Root cause notes, Countermeasures |
Tagsno overlap | SynthesisQualitativeRoot cause | QualityProblem solvingRoot cause | Domain-Driven DesignContextBoundaries | Root causeIncidentLeanProblem solving |