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 |  Systems Thinking Iceberg Model |  Operations MORT Analysis |  Systems Thinking Behavior Over Time Graph |
|---|---|---|---|---|
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. | The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | A Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | As needed | 30-60 min | Mehrere Tage bis Wochen | 20-45 min |
Participantsdifferent | 4-15 | 2-10 | 2-6 | 1-10 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Incident Log, Action Tracker, Stakeholder Updates | Iceberg Worksheet, Pattern Notes, Intervention Ideas | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Behavior Over Time Graph, Trend Hypotheses, Key Events |
Tagsno overlap | IncidentOperationsReliability | Systems thinkingRoot causePatterns | Root causeSafetySystemicIncident | Systems thinkingPatternsDynamics |