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 C4 Model |  UX Design Customer Journey Canvas |  Architecture Architecture Decision Record |  UX Research Customer Journey Mapping |
|---|---|---|---|---|
Purposedifferent | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 1-4 h | 1-3 h | 15-45 min | 2-4 h |
Participantsdifferent | 1-5 | 3-10 | 1-3 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Customer Journey Canvas, Pain Points, Experience Opportunities | ADR File, Decision Log, Rationale | Journey Map, Pain-point List, Opportunity Backlog |
Tagsno overlap | ArchitectureCommunicationVisualization | JourneyCustomerService designCanvas | ArchitectureRationaleDocumentationGovernance | JourneyServiceService design |