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 |  Domain Modeling Context Map |  Operations Fishbone Diagram |  Operations Root Cause Tree Analysis |
|---|---|---|---|---|
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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | Halber Tag | 1-3 h | 30-60 min | 1-3 h |
Participantsdifferent | 5-20 | 2-8 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Context Map, Integration Patterns, Boundary Notes | Fishbone Diagram, Cause Categories, Investigation Backlog | Cause Tree, Evidence Notes, Countermeasures |
Tagsno overlap | ResilienceOperationsIncident | Domain-Driven DesignBoundariesStrategy | Root causeQualityOperations | Root causeTreeIncidentQuality |