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 |  Facilitation Stakeholder Salience Model |  Delivery RAID Log |
|---|---|---|---|
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 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 60-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 10-50 | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Salience Diagram, Strategy per Class | RAID Log, Status Report Source |
Tagsno overlap | SatisfactionPrioritizationCustomer | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
