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 Rich Picture | ![]() Systems Thinking Soft Systems Methodology | ![]() Operations Learning Review |
|---|---|---|---|---|
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. | 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. | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | High | Low | High | Medium |
Timedifferent | Halber Tag | 30-90 min | 0.5-3 Tage | 1-3 h |
Participantsdifferent | 5-20 | 2-10 | 5-15 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Rich Picture, Problem Framing Notes | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | ResilienceOperationsIncident | Systems thinkingSoft systemsFramingVisualization | Soft systemsComplexitySensemakingSystems thinking | LearningRetrospectiveIncidentOperations |



