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 Design Service Blueprinting |  Operations RACI Matrix |  UX Design Customer Journey 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 service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible. | 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. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 15-45 min | 0.5-2 Tage | 45-90 min | 1-3 h |
Participantsdifferent | 1-3 | 6-12 | 2-8 | 3-10 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Service Blueprint, Fail Points, Ownership Map | RACI Matrix, Responsibility Map, Decision Notes | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Service designOperationsJourneyBlueprint | RolesResponsibilityGovernanceOperations | JourneyCustomerService designCanvas |