View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Dot Voting |  Engineering Kanban |  Delivery Monte Carlo Forecasting |  Delivery Cost of Delay |
|---|---|---|---|---|
Purposedifferent | When a workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. | 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. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | Low | Medium | High | High |
Timedifferent | 5-15 min | Ongoing | 30-90 min Setup, danach laufend | 90-180 min |
Participantsdifferent | 3-20 | 2-12 | 1-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Ranked list, Consensus signal, Shortlist | Kanban board, WIP policies, Flow metrics | Forecast Percentiles, Throughput Dataset, Risk Communication | CoD Table, Prioritization Sequence |
Tagsno overlap | FacilitationVotingConsensusPrioritization | FlowVisual managementDelivery | ForecastingFlowDelivery | PrioritizationDeliveryEconomicsDecision |