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 arc42 |  UX Design Service Blueprinting |  Architecture Architecture Decision Record |  UX Design Customer Journey Canvas |
|---|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. | 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 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 | 1-2 Tage | 0.5-2 Tage | 15-45 min | 1-3 h |
Participantsdifferent | 1-4 | 6-12 | 1-3 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Service Blueprint, Fail Points, Ownership Map | ADR File, Decision Log, Rationale | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | ArchitectureDocumentationCommunication | Service designOperationsJourneyBlueprint | ArchitectureRationaleDocumentationGovernance | JourneyCustomerService designCanvas |