View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Delphi Method |  Delivery Monte Carlo Forecasting |  Delivery Value Stream Mapping |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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. | 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. | 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. |
Complexitydifferent | High | High | Medium | Medium |
Timedifferent | 1-4 Wochen | 30-90 min Setup, danach laufend | 1-3 h | Ongoing |
Participantsdifferent | 6-30 Experten | 1-8 | 4-10 | 2-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Expert Forecast, Consensus Range, Assumption Notes | Forecast Percentiles, Throughput Dataset, Risk Communication | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | ForecastingExpertsDecisionStrategy | ForecastingFlowDelivery | LeanFlowWasteDelivery | FlowVisual managementDelivery |