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 Systems Mapping | ![]() Domain Modeling Bounded Context Canvas | ![]() Systems Thinking Intervention Mapping |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 1-3 h | 1-3 h | 1-5 Tage |
Participantsdifferent | 4-10 | 3-12 | 3-8 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | System Map, Dependencies, Leverage Points | Context Canvas, Glossary, Integration Notes | Logic Model, Change Objectives, Intervention Components, Evaluation Plan |
Tagsno overlap | LeanFlowWasteDelivery | Systems thinkingMappingBoundariesChange | Domain-Driven DesignBoundariesModeling | ChangeSystems thinkingCapability |



