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 After-Action Review |  Operations 5 Whys |  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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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 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 | 20-45 min | 15-30 min | 2-8 h |
Participantsdifferent | 2-5 | 3-12 | 2-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Lessons learned, Action items, Event summary | Root cause notes, Countermeasures | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | LeanProblem solvingCoachingOperations | LearningOperationsImprovement | Root causeIncidentLeanProblem solving | Problem solvingRoot causeDecisionOperations |