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 Design Customer Journey Canvas |  Architecture arc42 |  Architecture Software Architecture Canvas |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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 | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 1-2 Tage | 1-2 h | 15-45 min |
Participantsdifferent | 3-10 | 1-4 | 3-10 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Architecture Document, Context View, Runtime View, Deployment View | Architecture Canvas, Goals, Constraints, Quality Attributes | ADR File, Decision Log, Rationale |
Tagsno overlap | JourneyCustomerService designCanvas | ArchitectureDocumentationCommunication | CanvasArchitectureAlignmentWorkshop | ArchitectureRationaleDocumentationGovernance |