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 Blameless Postmortem |  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. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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 | 30-90 min | Halber Tag | 45-90 min |
Participantsdifferent | 2-10 | 3-12 | 5-20 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Rich Picture, Problem Framing Notes | Postmortem Doc, Action Items, Timeline | Simulation Notes, Gaps List, Updated Runbooks | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | Systems thinkingSoft systemsFramingVisualization | Site Reliability EngineeringIncidentLearningReliability | ResilienceOperationsIncident | Systems thinkingFramingStakeholders |