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 Force Field Analysis |  Decision Making OODA Loop |
|---|---|---|---|---|
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 change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-3 h | 45-90 min | 15-60 min je Zyklus |
Participantsdifferent | 4-10 | 2-8 | 3-12 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Context Map, Integration Patterns, Boundary Notes | Force Field Map, Change Levers, Risk Notes | Situation Assessment, Decision Loop, Action Updates |
Tagsno overlap | LeanFlowWasteDelivery | Domain-Driven DesignBoundariesStrategy | ChangeDecisionStrategy | DecisionChangeLearningStrategy |