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 | ![]() UX Research Affinity Diagramming | ![]() Architecture Risk Storming |
|---|---|---|---|---|
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. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-45 min | 30–60 min | 45–90 min | 60-90 min |
Participantsdifferent | 1-3 | 4-8 | 3-10 | 4-12 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Empathy Map, Assumptions List, Research Gaps | Theme clusters, Insight statements, Opportunity areas | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | SynthesisQualitativeWorkshop | SynthesisQualitativeRoot cause | RiskArchitectureWorkshopValidation |



