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 Jobs to Be Done |  Product Discovery Kano Model |  Product Strategy Impact Mapping |  Business Strategy Scenario Planning |
|---|---|---|---|---|
Purposedifferent | 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 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 a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 Wochen | 1-2 Tage | 45-90 min | 0.5-2 Tage |
Participantsdifferent | 5-12 Interviews | 10-50 | 3-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Kano Matrix, Feature Classes, Priority Themes | Impact Map, Outcome Hypotheses, Delivery Options | Scenario Set, Strategic Implications, Robust Options |
Tagsno overlap | CustomerOutcomesNeeds | SatisfactionPrioritizationCustomer | OutcomesStrategyBehaviorPlanning | StrategyUncertaintyPlanning |