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 C4 Model |  Architecture Software Architecture Canvas |
|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 h | 1-4 h | 1-2 h |
Participantsdifferent | 3-10 | 1-5 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Context Diagram, Container Diagram, Component Diagram | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | JourneyCustomerService designCanvas | ArchitectureCommunicationVisualization | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
