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 |  UX Research User Interviews |  Product Discovery Opportunity Solution Tree |  Product Discovery Opportunity Interview |
|---|---|---|---|---|
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 teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-6 h | 30–60 min per interview | 1-2 h Setup, laufend | 30-60 min je Interview |
Participantsdifferent | 2-8 | 1 participant per interview | 2-6 | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Interview Notes, Themes, Insight Summary | Opportunity Solution Tree, Experiment Backlog, Learning Log | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | QualitativeResearchCustomerDiscovery | DiscoveryOutcomesExperimentsOpportunity | DiscoveryInterviewsOpportunityCustomer |