View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Empathy MappingCustomer Journey CanvasArchitecture Decision RecordSoftware Architecture Canvas
| Criterion |  UX Research Empathy Mapping |  UX Design Customer Journey Canvas |  Architecture Architecture Decision Record |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
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. | When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. | 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. | 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 | Medium | Low | Low |
Timedifferent | 30–60 min | 1-3 h | 15-45 min | 1-2 h |
Participantsdifferent | 4-8 | 3-10 | 1-3 | 3-10 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Empathy Map, Assumptions List, Research Gaps | Customer Journey Canvas, Pain Points, Experience Opportunities | ADR File, Decision Log, Rationale | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | SynthesisQualitativeWorkshop | JourneyCustomerService designCanvas | ArchitectureRationaleDocumentationGovernance | CanvasArchitectureAlignmentWorkshop |