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 Runbook |  Operations Weekly Review |  Operations Getting Things Done |
|---|---|---|---|---|
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. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Halber Tag | 20-60 min | 30-60 min | 1-2 h Setup, laufend |
Participantsdifferent | 5-20 | 1-4 | 1 | 1 |
Formatdifferent | Workshop | Async | Async | Async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Runbook, Checklist, Escalation Path | Updated Task System, Weekly Focus, Next Actions | Action Lists, Project List, Review Routine |
Tagsno overlap | ResilienceOperationsIncident | OperationsReliabilityDocumentation | ProductivityExecutionPlanning | ProductivityPlanningTasksExecution |