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 |  Architecture Architecture Decision Record |  Domain Modeling EventStorming |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-60 min je Interview | 2-6 h | 15-45 min | 2-8 h |
Participantsdifferent | 5-12 Interviews | 2-8 | 1-3 | 5-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Event Model, UI Flow, Commands, Read Models | ADR File, Decision Log, Rationale | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | EventsBlueprintDomain-Driven DesignBehavior | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignEventsDiscoveryWorkshop |