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 Force Field Analysis | ![]() Delivery Monte Carlo Forecasting | ![]() Product Strategy DIBB |
|---|---|---|---|---|
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 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 h | 45-90 min | 30-90 min Setup, danach laufend | 1-2 h |
Participantsdifferent | 4-10 | 3-12 | 1-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Force Field Map, Change Levers, Risk Notes | Forecast Percentiles, Throughput Dataset, Risk Communication | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | LeanFlowWasteDelivery | ChangeDecisionStrategy | ForecastingFlowDelivery | StrategyDecisionAssumptionsHypothesis |



