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 Empathy Mapping |  Architecture Quality Attribute Workshop |
|---|---|---|---|---|
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 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 2-8 h | 30–60 min | 2-4 h |
Participantsdifferent | 1-3 | 5-12 | 4-8 | 5-15 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Empathy Map, Assumptions List, Research Gaps | Quality Scenarios, Priority List, Architecture Concerns |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignEventsDiscoveryWorkshop | SynthesisQualitativeWorkshop | RequirementsArchitectureWorkshop |