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 Empathy Mapping |  Knowledge Modeling Event Modeling |  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 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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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 | Low | Medium | Low |
Timedifferent | 15-45 min | 30–60 min | 2-6 h | 45–90 min |
Participantsdifferent | 1-3 | 4-8 | 2-8 | 3-10 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Empathy Map, Assumptions List, Research Gaps | Event Model, UI Flow, Commands, Read Models | Theme clusters, Insight statements, Opportunity areas |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | SynthesisQualitativeWorkshop | EventsBlueprintDomain-Driven DesignBehavior | SynthesisQualitativeRoot cause |