View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:C4 ModelArchitecture Decision RecordCustomer Journey CanvasArchitecture Communication Canvas
| Criterion |  Architecture C4 Model |  Architecture Architecture Decision Record |  UX Design Customer Journey Canvas |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1-4 h | 15-45 min | 1-3 h | 60-120 min |
Participantsdifferent | 1-5 | 1-3 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | Customer Journey Canvas, Pain Points, Experience Opportunities | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | JourneyCustomerService designCanvas | ArchitectureCommunicationStakeholdersCanvas |