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 Value Stream Mapping |  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. | 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 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 | Medium | Medium | Low |
Timedifferent | Ongoing | 1-3 h | 1-3 h | 5-15 min |
Participantsdifferent | 2-12 | 4-10 | 5-30 | 3-20 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list | Consensus Clusters, Theme Titles, Priority Areas | Ranked list, Consensus signal, Shortlist |
Tagsno overlap | FlowVisual managementDelivery | LeanFlowWasteDelivery | FacilitationConsensusWorkshopAlignment | FacilitationVotingConsensusPrioritization |