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 |  Systems Thinking CATWOE Analysis |  Systems Thinking Rich Picture |  Operations 5 Whys |
|---|---|---|---|---|
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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Halber Tag | 45-90 min | 30-90 min | 15-30 min |
Participantsdifferent | 5-20 | 3-8 | 2-10 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Rich Picture, Problem Framing Notes | Root cause notes, Countermeasures |
Tagsno overlap | ResilienceOperationsIncident | Systems thinkingFramingStakeholders | Systems thinkingSoft systemsFramingVisualization | Root causeIncidentLeanProblem solving |