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 | ![]() Business Strategy Business Model Stress Test | ![]() Knowledge Modeling Knowledge Mapping | ![]() 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 h | Half day | 1-3 h | 1-2 h |
Participantsdifferent | 3-8 | 3-8 | 3-12 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Stress Test Report, Action Plan per Scenario | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | FailureResilienceRisk | StrategyBusiness modelRiskDiagnosis | KnowledgeMappingRisk | KnowledgeConceptsMappingSensemaking |



