View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordEmpathy MappingDecision Rights MappingSoftware Architecture Canvas
| Criterion | ![]() Architecture Architecture Decision Record | ![]() UX Research Empathy Mapping | ![]() Decision Making Decision Rights Mapping | ![]() Architecture Software Architecture Canvas |
|---|---|---|---|---|
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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 30–60 min | 90-180 min | 1-2 h |
Participantsdifferent | 1-3 | 4-8 | 4-12 | 3-10 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Empathy Map, Assumptions List, Research Gaps | Decision Rights Matrix, Agreement | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | SynthesisQualitativeWorkshop | DecisionGovernanceAlignmentResponsibility | CanvasArchitectureAlignmentWorkshop |



