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 Solution Tree |  UX Research Empathy Mapping |  Domain Modeling EventStorming |
|---|---|---|---|---|
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 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. | When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. | 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 | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 1-2 h Setup, laufend | 30–60 min | 2-8 h |
Participantsdifferent | 1-3 | 2-6 | 4-8 | 5-12 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Opportunity Solution Tree, Experiment Backlog, Learning Log | Empathy Map, Assumptions List, Research Gaps | Event Timeline, Ubiquitous Language, Boundaries, Open Questions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | DiscoveryOutcomesExperimentsOpportunity | SynthesisQualitativeWorkshop | Domain-Driven DesignEventsDiscoveryWorkshop |