View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Event Modeling |  Product Discovery Opportunity Interview |  Product Discovery Opportunity Scoring |  Product Discovery Opportunity Solution Tree |
|---|---|---|---|---|
Purposedifferent | 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 are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | 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 discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2-6 h | 30-60 min je Interview | 60-120 min | 1-2 h Setup, laufend |
Participantsdifferent | 2-8 | 5-12 Interviews | 3-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Interview Notes, Opportunity Themes, Customer Quotes | Opportunity Score Table, Top Outcomes | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | DiscoveryInterviewsOpportunityCustomer | PrioritizationDiscoveryOutcomesNeeds | DiscoveryOutcomesExperimentsOpportunity |