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 |  Domain Modeling Domain Context Map |  Systems Thinking Intervention 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. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 1-3 h | 1-3 h | 1-5 Tage |
Participantsdifferent | 3-8 | 3-10 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Domain Context Map, Boundary Notes, Ownership Map | Logic Model, Change Objectives, Intervention Components, Evaluation Plan |
Tagsno overlap | FailureResilienceRisk | Domain-Driven DesignContextBoundaries | ChangeSystems thinkingCapability |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
