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