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 Sailboat Retrospective |  Agile Start Stop Continue |  Operations Learning 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. | 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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Halber Tag | 45-90 min | 30-60 min | 1-3 h |
Participantsdifferent | 5-20 | 4-12 | 3-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Sailboat Board, Risks, Improvement Actions | Start Stop Continue Board, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | ResilienceOperationsIncident | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection | LearningRetrospectiveIncidentOperations |