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 |  Systems Thinking Future Reality Tree |  Operations Family Tree Analysis |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | 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. | 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. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 60-120 min | 2-4 h | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 2-8 | 3-8 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Family Tree Diagram, Pattern Notes, Systemic Measures | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Theory of ConstraintsSystems thinkingChange | Root causePatternsIncidentSystemic | Root causeSafetySystemicIncident |