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 |  Architecture Architecture Decision Record |  Operations A3 Problem Solving |  Architecture arc42 |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-30 min | 15-45 min | 45-90 min | 1-2 Tage |
Participantsdifferent | 2-6 | 1-3 | 2-5 | 1-4 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | ADR File, Decision Log, Rationale | A3 Report, Action Plan, Root Cause Analysis | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Root causeIncidentLeanProblem solving | ArchitectureRationaleDocumentationGovernance | LeanProblem solvingCoachingOperations | ArchitectureDocumentationCommunication |