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 Monte Carlo Forecasting |  Operations A3 Problem Solving |  Operations 5 Whys |  Delivery Value Stream Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | 30-90 min Setup, danach laufend | 45-90 min | 15-30 min | 1-3 h |
Participantsdifferent | 1-8 | 2-5 | 2-6 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | A3 Report, Action Plan, Root Cause Analysis | Root cause notes, Countermeasures | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | ForecastingFlowDelivery | LeanProblem solvingCoachingOperations | Root causeIncidentLeanProblem solving | LeanFlowWasteDelivery |