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 |  Delivery RAID Log |  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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | Low | Low |
Timedifferent | Halber Tag | 30 min Setup, dann laufend | 20-45 min |
Participantsdifferent | 5-20 | 1-3 maintaining, briefing for everyone | 3-12 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | RAID Log, Status Report Source | Lessons learned, Action items, Event summary |
Tagsno overlap | ResilienceOperationsIncident | RiskTrackingStakeholdersGovernance | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
