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 MORT Analysis |  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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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 | High | Low | Medium |
Timedifferent | 30-90 min Setup, danach laufend | Mehrere Tage bis Wochen | 15-30 min | 1-3 h |
Participantsdifferent | 1-8 | 2-6 | 2-6 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Root cause notes, Countermeasures | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | ForecastingFlowDelivery | Root causeSafetySystemicIncident | Root causeIncidentLeanProblem solving | LeanFlowWasteDelivery |