View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Rich Picture |  DevOps Incident Command |  DevOps Game Day |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 30-90 min | As needed | Halber Tag | 45-90 min |
Participantsdifferent | 2-10 | 4-15 | 5-20 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Rich Picture, Problem Framing Notes | Incident Log, Action Tracker, Stakeholder Updates | Simulation Notes, Gaps List, Updated Runbooks | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | Systems thinkingSoft systemsFramingVisualization | IncidentOperationsReliability | ResilienceOperationsIncident | Systems thinkingFramingStakeholders |