View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Game Day |  Operations A3 Problem Solving |  Operations After-Action Review |
|---|---|---|---|
Purposedifferent | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | 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. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Halber Tag | 45-90 min | 20-45 min |
Participantsdifferent | 5-20 | 2-5 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | A3 Report, Action Plan, Root Cause Analysis | Lessons learned, Action items, Event summary |
Tags1 shared | ResilienceOperationsIncident | LeanProblem solvingCoachingOperations | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
