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 Learning Review |  Agile Sailboat Retrospective |  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. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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 | Low |
Timedifferent | Halber Tag | 1-3 h | 45-90 min | 20-45 min |
Participantsdifferent | 5-20 | 3-10 | 4-12 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Learning Review Notes, System Factors, Improvement Actions | Sailboat Board, Risks, Improvement Actions | Lessons learned, Action items, Event summary |
Tagsno overlap | ResilienceOperationsIncident | LearningRetrospectiveIncidentOperations | RetrospectiveTeamImprovement | LearningOperationsImprovement |