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 Opportunity Scoring |  Product Discovery Kano Model |  Domain Modeling EventStorming |  Product Discovery Jobs to Be Done |
|---|---|---|---|---|
Purposedifferent | When opportunities need ranking by their effect, it makes importance and satisfaction directly comparable. It separates problem, assumption, solution, and evidence. The result is captured as an opportunity-score table and top outcomes. | 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 domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 60-120 min | 1-2 Tage | 2-8 h | 1-3 Wochen |
Participantsdifferent | 3-6 | 10-50 | 5-12 | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Opportunity Score Table, Top Outcomes | Kano Matrix, Feature Classes, Priority Themes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Job Stories, Outcome Statements, Opportunity List |
Tagsno overlap | PrioritizationDiscoveryOutcomesNeeds | SatisfactionPrioritizationCustomer | Domain-Driven DesignEventsDiscoveryWorkshop | CustomerOutcomesNeeds |