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 |  Decision Making OODA Loop |  Engineering Kanban |  Delivery Cost of Delay |
|---|---|---|---|---|
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. | 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 work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 15-60 min je Zyklus | Ongoing | 90-180 min |
Participantsdifferent | 4-10 | 1-8 | 2-12 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Situation Assessment, Decision Loop, Action Updates | Kanban board, WIP policies, Flow metrics | CoD Table, Prioritization Sequence |
Tagsno overlap | LeanFlowWasteDelivery | DecisionChangeLearningStrategy | FlowVisual managementDelivery | PrioritizationDeliveryEconomicsDecision |