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 A3 Problem Solving |  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 a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 | Medium | Low | Medium |
Timedifferent | Halber Tag | 45-90 min | 15-45 min | As needed |
Participantsdifferent | 5-20 | 2-5 | 1-3 | 4-15 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | A3 Report, Action Plan, Root Cause Analysis | ADR File, Decision Log, Rationale | Incident Log, Action Tracker, Stakeholder Updates |
Tagsno overlap | ResilienceOperationsIncident | LeanProblem solvingCoachingOperations | ArchitectureRationaleDocumentationGovernance | IncidentOperationsReliability |