View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Bottleneck Analysis | ![]() Engineering Kanban | ![]() Facilitation Consensus Workshop | ![]() Facilitation Dot Voting |
|---|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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 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 | 1-3 h | Ongoing | 1-3 h | 5-15 min |
Participantsdifferent | 3-8 | 2-12 | 5-30 | 3-20 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Kanban board, WIP policies, Flow metrics | Consensus Clusters, Theme Titles, Priority Areas | Ranked list, Consensus signal, Shortlist |
Tagsno overlap | FlowMeasurementConstraints | FlowVisual managementDelivery | FacilitationConsensusWorkshopAlignment | FacilitationVotingConsensusPrioritization |



