View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Value Stream Mapping | ![]() Systems Thinking Intervention Mapping | ![]() Domain Modeling Context Map |
|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 h | 1-5 Tage | 1-3 h |
Participantsdifferent | 4-10 | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | LeanFlowWasteDelivery | ChangeSystems thinkingCapability | Domain-Driven DesignBoundariesStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






