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 |  Knowledge Modeling Knowledge Mapping |  Systems Thinking Evaporating Cloud |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 h | 60-120 min | 1-2 h |
Participantsdifferent | 3-8 | 3-12 | 2-8 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | FailureResilienceRisk | KnowledgeMappingRisk | Theory of ConstraintsAssumptionsSystems thinking | KnowledgeConceptsMappingSensemaking |