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 |  Delivery MoSCoW |  Product Discovery Kano Model |
|---|---|---|---|
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 a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 Wochen | 30-90 min | 1-2 Tage |
Participantsdifferent | 5-12 Interviews | 3-12 | 10-50 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Prioritized Backlog, Release Scope, Tradeoff Notes | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | CustomerOutcomesNeeds | PrioritizationScopeDecision | SatisfactionPrioritizationCustomer |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
