View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Product Discovery Kano Model | ![]() Agile WSJF | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-2 Tage | 45-90 min | 60-90 min |
Participantsdifferent | 10-50 | 3-10 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Ranked Backlog, Cost-of-Delay Assumptions | Salience Diagram, Strategy per Class |
Tagsno overlap | SatisfactionPrioritizationCustomer | LeanEconomicsSequencePrioritization | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






