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 |  Facilitation Consensus Workshop |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
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 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | Ongoing | 1-3 h | 60-90 min |
Participantsdifferent | 2-12 | 5-30 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Consensus Clusters, Theme Titles, Priority Areas | Salience Diagram, Strategy per Class |
Tagsno overlap | FlowVisual managementDelivery | FacilitationConsensusWorkshopAlignment | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
