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 Incident Command |  Operations Runbook |  Systems Thinking Rich Picture |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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 | Medium | Low | Low | Medium |
Timedifferent | As needed | 20-60 min | 30-90 min | 45-90 min |
Participantsdifferent | 4-15 | 1-4 | 2-10 | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Incident Log, Action Tracker, Stakeholder Updates | Runbook, Checklist, Escalation Path | Rich Picture, Problem Framing Notes | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | IncidentOperationsReliability | OperationsReliabilityDocumentation | Systems thinkingSoft systemsFramingVisualization | Systems thinkingFramingStakeholders |