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 |  Facilitation Consensus Workshop |  Facilitation Dot Voting |
|---|---|---|---|---|
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 group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | Ongoing | 30-90 min Setup, danach laufend | 1-3 h | 5-15 min |
Participantsdifferent | 2-12 | 1-8 | 5-30 | 3-20 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Forecast Percentiles, Throughput Dataset, Risk Communication | Consensus Clusters, Theme Titles, Priority Areas | Ranked list, Consensus signal, Shortlist |
Tagsno overlap | FlowVisual managementDelivery | ForecastingFlowDelivery | FacilitationConsensusWorkshopAlignment | FacilitationVotingConsensusPrioritization |