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 Problem Interview |  Domain Modeling EventStorming |  Architecture Architecture Decision Record |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 30-60 min je Interview | 2-8 h | 15-45 min |
Participantsdifferent | 5-12 Interviews | 5-12 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | ADR File, Decision Log, Rationale |
Tagsno overlap | DiscoveryInterviewsValidation | Domain-Driven DesignEventsDiscoveryWorkshop | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
