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 Opportunity Interview |  Knowledge Modeling Event Modeling |  Product Discovery Opportunity Scoring |
|---|---|---|---|---|
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 opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 30-60 min je Interview | 2-6 h | 60-120 min |
Participantsdifferent | 5-12 Interviews | 5-12 Interviews | 2-8 | 3-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Interview Notes, Opportunity Themes, Customer Quotes | Event Model, UI Flow, Commands, Read Models | Opportunity Score Table, Top Outcomes |
Tagsno overlap | CustomerOutcomesNeeds | DiscoveryInterviewsOpportunityCustomer | EventsBlueprintDomain-Driven DesignBehavior | PrioritizationDiscoveryOutcomesNeeds |