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 A3 Problem Solving |  Operations 5 Whys |  Architecture Architecture Decision Record |  Operations Kepner-Tregoe |
|---|---|---|---|---|
Purposedifferent | 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. | 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 45-90 min | 15-30 min | 15-45 min | 2-8 h |
Participantsdifferent | 2-5 | 2-6 | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Root cause notes, Countermeasures | ADR File, Decision Log, Rationale | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | LeanProblem solvingCoachingOperations | Root causeIncidentLeanProblem solving | ArchitectureRationaleDocumentationGovernance | Problem solvingRoot causeDecisionOperations |