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 4Ls 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 sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Halber Tag | 30-60 min | 20-45 min | 45–75 min |
Participantsdifferent | 5-20 | 3-10 | 3-12 | Team members involved |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Emotion Board, Themes, Action Items | Lessons learned, Action items, Event summary | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ResilienceOperationsIncident | RetrospectiveTeamReflection | LearningOperationsImprovement | RetrospectiveLearningReflectionTeam |