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 Customer Journey Canvas |  Architecture Architecture Decision Record |  Architecture C4 Model |
|---|---|---|---|---|
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 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 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-2 Tage | 1-3 h | 15-45 min | 1-4 h |
Participantsdifferent | 1-4 | 3-10 | 1-3 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Customer Journey Canvas, Pain Points, Experience Opportunities | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ArchitectureDocumentationCommunication | JourneyCustomerService designCanvas | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization |