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 |  Decision Making OODA Loop |  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. | 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. | 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 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 h | 15-60 min je Zyklus | 1-3 h |
Participantsdifferent | 4-10 | 3-12 | 1-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | System Map, Dependencies, Leverage Points | Situation Assessment, Decision Loop, Action Updates | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | LeanFlowWasteDelivery | Systems thinkingMappingBoundariesChange | DecisionChangeLearningStrategy | Domain-Driven DesignBoundariesStrategy |