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 Interview |  Knowledge Modeling Event Modeling |  UX Research User Interviews |  UX Research Personas |
|---|---|---|---|---|
Purposedifferent | 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 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 target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-60 min je Interview | 2-6 h | 30–60 min per interview | 1-3 Tage |
Participantsdifferent | 5-12 Interviews | 2-8 | 1 participant per interview | Internes Team |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Event Model, UI Flow, Commands, Read Models | Interview Notes, Themes, Insight Summary | Persona Profiles, Needs Summary, Scenario Notes |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | EventsBlueprintDomain-Driven DesignBehavior | QualitativeResearchCustomerDiscovery | ResearchCustomerSynthesis |