View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Engineering Failure Scenario Analysis | ![]() Systems Thinking Evaporating Cloud | ![]() Knowledge Modeling Concept Mapping | ![]() Systems Thinking Future Reality Tree |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 60-120 min | 1-2 h | 2-4 h |
Participantsdifferent | 3-8 | 2-8 | 1-8 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Concept Map, Relationship Labels, Knowledge Gaps | Future Reality Tree, Negative Branches, Assumption List, Improved Injections |
Tagsno overlap | FailureResilienceRisk | Theory of ConstraintsAssumptionsSystems thinking | KnowledgeConceptsMappingSensemaking | Theory of ConstraintsSystems thinkingChange |



