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 Alignment Mapping |  Domain Modeling Context Map |  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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | Medium |
Timedifferent | 1-2 Tage | 1-2 h | 1-3 h | 60-90 min |
Participantsdifferent | 10-50 | 4-12 | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Alignment Map, Open Issues, Decision Questions | Context Map, Integration Patterns, Boundary Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | SatisfactionPrioritizationCustomer | AlignmentStakeholdersStrategyFacilitation | Domain-Driven DesignBoundariesStrategy | StakeholdersFacilitationAlignmentGovernance |