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 |  Architecture C4 Model |  Operations 5 Whys |  Operations Kepner-Tregoe |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | High | Low | Low | High |
Timedifferent | Halber Tag | 1-4 h | 15-30 min | 2-8 h |
Participantsdifferent | 5-20 | 1-5 | 2-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Context Diagram, Container Diagram, Component Diagram | Root cause notes, Countermeasures | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | ResilienceOperationsIncident | ArchitectureCommunicationVisualization | Root causeIncidentLeanProblem solving | Problem solvingRoot causeDecisionOperations |