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 Service Blueprinting |  Architecture Software Architecture Canvas |  UX Design Customer Journey 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. | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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. | 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. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 1-4 h | 0.5-2 Tage | 1-2 h | 1-3 h |
Participantsdifferent | 1-5 | 6-12 | 3-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Service Blueprint, Fail Points, Ownership Map | Architecture Canvas, Goals, Constraints, Quality Attributes | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | ArchitectureCommunicationVisualization | Service designOperationsJourneyBlueprint | CanvasArchitectureAlignmentWorkshop | JourneyCustomerService designCanvas |