View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Runbook |  Decision Making Argument Mapping |  DevOps Game Day |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 20-60 min | 1-3 h | Halber Tag | 15-45 min |
Participantsdifferent | 1-4 | 1-8 | 5-20 | 1-3 |
Formatdifferent | Async | Workshop + async | Workshop | Async |
Outputdifferent | Runbook, Checklist, Escalation Path | Argument Map, Evidence Gaps, Decision Rationale | Simulation Notes, Gaps List, Updated Runbooks | ADR File, Decision Log, Rationale |
Tagsno overlap | OperationsReliabilityDocumentation | SensemakingDecisionRationale | ResilienceOperationsIncident | ArchitectureRationaleDocumentationGovernance |