View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Delivery Monte Carlo Forecasting |  Product Strategy Impact Mapping |  Decision Making Delphi Method |
|---|---|---|---|---|
Purposedifferent | 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. | 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 a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | Ongoing | 30-90 min Setup, danach laufend | 45-90 min | 1-4 Wochen |
Participantsdifferent | 2-12 | 1-8 | 3-8 | 6-30 Experten |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Forecast Percentiles, Throughput Dataset, Risk Communication | Impact Map, Outcome Hypotheses, Delivery Options | Expert Forecast, Consensus Range, Assumption Notes |
Tagsno overlap | FlowVisual managementDelivery | ForecastingFlowDelivery | OutcomesStrategyBehaviorPlanning | ForecastingExpertsDecisionStrategy |