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 |  UX Research User Interviews |  Domain Modeling EventStorming |  Product Discovery Opportunity 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 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 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 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 | Low | Low | Medium | Medium |
Timedifferent | 15-45 min | 30–60 min per interview | 2-8 h | 30-60 min je Interview |
Participantsdifferent | 1-3 | 1 participant per interview | 5-12 | 5-12 Interviews |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Interview Notes, Themes, Insight Summary | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | QualitativeResearchCustomerDiscovery | Domain-Driven DesignEventsDiscoveryWorkshop | DiscoveryInterviewsOpportunityCustomer |