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 |  Domain Modeling EventStorming |  UX Research Affinity Diagramming |
|---|---|---|---|
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 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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 15-45 min | 2-8 h | 45–90 min |
Participantsdifferent | 1-3 | 5-12 | 3-10 |
Formatdifferent | Async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Theme clusters, Insight statements, Opportunity areas |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignEventsDiscoveryWorkshop | SynthesisQualitativeRoot cause |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
