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 Context Map |  Decision Making OODA Loop |  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 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. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 h | 15-60 min je Zyklus | 1-3 h |
Participantsdifferent | 4-10 | 2-8 | 1-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Context Map, Integration Patterns, Boundary Notes | Situation Assessment, Decision Loop, Action Updates | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | LeanFlowWasteDelivery | Domain-Driven DesignBoundariesStrategy | DecisionChangeLearningStrategy | Domain-Driven DesignBoundariesModeling |