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 Concept Mapping |  UX Research User Interviews |  Knowledge Modeling Event Modeling |  Product Discovery Opportunity Interview |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-2 h | 30–60 min per interview | 2-6 h | 30-60 min je Interview |
Participantsdifferent | 1-8 | 1 participant per interview | 2-8 | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Interview Notes, Themes, Insight Summary | Event Model, UI Flow, Commands, Read Models | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | QualitativeResearchCustomerDiscovery | EventsBlueprintDomain-Driven DesignBehavior | DiscoveryInterviewsOpportunityCustomer |