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 |  Agile Mad Sad Glad |  Operations After-Action Review |  Agile Sailboat Retrospective |
|---|---|---|---|---|
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 a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. | 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. | 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Halber Tag | 30-60 min | 20-45 min | 45-90 min |
Participantsdifferent | 5-20 | 3-10 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Emotion Board, Themes, Action Items | Lessons learned, Action items, Event summary | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | ResilienceOperationsIncident | RetrospectiveTeamReflection | LearningOperationsImprovement | RetrospectiveTeamImprovement |