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 Intervention Mapping |  Domain Modeling Context Map |  Systems Thinking Systems 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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 h | 1-5 Tage | 1-3 h | 1-3 h |
Participantsdifferent | 3-8 | 4-12 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Context Map, Integration Patterns, Boundary Notes | System Map, Dependencies, Leverage Points |
Tagsno overlap | FailureResilienceRisk | ChangeSystems thinkingCapability | Domain-Driven DesignBoundariesStrategy | Systems thinkingMappingBoundariesChange |