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 |  Architecture Architecture Decision Record |  DevOps Incident Command |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Halber Tag | 20-60 min | 15-45 min | As needed |
Participantsdifferent | 5-20 | 1-4 | 1-3 | 4-15 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Runbook, Checklist, Escalation Path | ADR File, Decision Log, Rationale | Incident Log, Action Tracker, Stakeholder Updates |
Tagsno overlap | ResilienceOperationsIncident | OperationsReliabilityDocumentation | ArchitectureRationaleDocumentationGovernance | IncidentOperationsReliability |