View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Empathy Mapping | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Architecture Architecture Decision Record |
|---|---|---|---|
Purposedifferent | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 30–60 min | 2–4 h review as a planning range; preparation and evaluation additional | 15-45 min |
Participantsdifferent | 4-8 | Designers, developers as users, and facilitation | 1-3 |
Formatdifferent | Workshop | Workshop + async | Async |
Outputdifferent | Empathy Map, Assumptions List, Research Gaps | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | ADR File, Decision Log, Rationale |
Tagsno overlap | SynthesisQualitativeWorkshop | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






