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 A3 Problem Solving |  Architecture arc42 |  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 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. | 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 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 | Medium | Low | Low |
Timedifferent | 45–90 min | 45-90 min | 1-2 Tage | 15-30 min |
Participantsdifferent | 3-10 | 2-5 | 1-4 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | A3 Report, Action Plan, Root Cause Analysis | Architecture Document, Context View, Runtime View, Deployment View | Root cause notes, Countermeasures |
Tagsno overlap | SynthesisQualitativeRoot cause | LeanProblem solvingCoachingOperations | ArchitectureDocumentationCommunication | Root causeIncidentLeanProblem solving |