View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations 5 Whys |  Operations A3 Problem Solving |  Architecture arc42 |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-30 min | 45-90 min | 1-2 Tage | 1-4 h |
Participantsdifferent | 2-6 | 2-5 | 1-4 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | A3 Report, Action Plan, Root Cause Analysis | Architecture Document, Context View, Runtime View, Deployment View | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | Root causeIncidentLeanProblem solving | LeanProblem solvingCoachingOperations | ArchitectureDocumentationCommunication | Root causeProblem solvingQualityIncident |