View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Waste Analysis | ![]() Delivery RAID Log | ![]() Delivery Value Stream Mapping | ![]() Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 45-120 min | 30 min Setup, dann laufend | 1-3 h | 30-90 min Setup, danach laufend |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 4-10 | 1-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | RAID Log, Status Report Source | Current-state map, Future-state map, Bottleneck list | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | WasteLeanProcess improvement | RiskTrackingStakeholdersGovernance | LeanFlowWasteDelivery | ForecastingFlowDelivery |



