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 Evaporating Cloud |  Operations MORT Analysis |  Systems Thinking Iceberg Model |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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 series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 60-120 min | Mehrere Tage bis Wochen | 30-60 min | 2-4 h |
Participantsdifferent | 2-8 | 2-6 | 2-10 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Root causeSafetySystemicIncident | Systems thinkingRoot causePatterns | Root causePatternsIncidentSystemic |