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 5 Whys |  Architecture arc42 |  Operations A3 Problem Solving |
|---|---|---|---|---|
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 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45–90 min | 15-30 min | 1-2 Tage | 45-90 min |
Participantsdifferent | 3-10 | 2-6 | 1-4 | 2-5 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Root cause notes, Countermeasures | Architecture Document, Context View, Runtime View, Deployment View | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | SynthesisQualitativeRoot cause | Root causeIncidentLeanProblem solving | ArchitectureDocumentationCommunication | LeanProblem solvingCoachingOperations |