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 Gemba Walk |  Operations After-Action Review |  Operations A3 Problem Solving |
|---|---|---|---|---|
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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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 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. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Halber Tag | 30-120 min | 20-45 min | 45-90 min |
Participantsdifferent | 5-20 | 2-6 | 3-12 | 2-5 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Observation Notes, Improvement Ideas | Lessons learned, Action items, Event summary | A3 Report, Action Plan, Root Cause Analysis |
Tags1 shared | ResilienceOperationsIncident | LeanObservationProcessOperations | LearningOperationsImprovement | LeanProblem solvingCoachingOperations |