View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Product Discovery Opportunity Interview |  Domain Modeling EventStorming |  Product Discovery Problem Interview |
|---|---|---|---|---|
Purposedifferent | 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 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. | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | 30-60 min je Interview | 2-8 h | 30-60 min je Interview |
Participantsdifferent | 1-3 | 5-12 Interviews | 5-12 | 5-12 Interviews |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Interview Notes, Opportunity Themes, Customer Quotes | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Problem Evidence, Risk Notes, Customer Segments |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | DiscoveryInterviewsOpportunityCustomer | Domain-Driven DesignEventsDiscoveryWorkshop | DiscoveryInterviewsValidation |