View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling EventStorming |  Architecture Architecture Decision Record |  Product Discovery Opportunity Interview |  Product Discovery Opportunity Solution Tree |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2-8 h | 15-45 min | 30-60 min je Interview | 1-2 h Setup, laufend |
Participantsdifferent | 5-12 | 1-3 | 5-12 Interviews | 2-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | ADR File, Decision Log, Rationale | Interview Notes, Opportunity Themes, Customer Quotes | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | Domain-Driven DesignEventsDiscoveryWorkshop | ArchitectureRationaleDocumentationGovernance | DiscoveryInterviewsOpportunityCustomer | DiscoveryOutcomesExperimentsOpportunity |