View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Domain Modeling Bounded Context Canvas | ![]() Systems Thinking Intervention Mapping | ![]() Systems Thinking Evaporating Cloud | ![]() Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 h | 1-5 Tage | 60-120 min | 1-3 h |
Participantsdifferent | 3-8 | 4-12 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Canvas, Glossary, Integration Notes | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | Domain-Driven DesignBoundariesModeling | ChangeSystems thinkingCapability | Theory of ConstraintsAssumptionsSystems thinking | Domain-Driven DesignBoundariesStrategy |



