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 |  Product Discovery Jobs to Be Done |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 1-3 Wochen | 60–90 min |
Participantsdifferent | 10-50 | 5-12 Interviews | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Job Stories, Outcome Statements, Opportunity List | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | SatisfactionPrioritizationCustomer | CustomerOutcomesNeeds | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
