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 Service Blueprinting |  Architecture C4 Model |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | 0.5-2 Tage | 1-4 h | 15-45 min | 1-2 Tage |
Participantsdifferent | 6-12 | 1-5 | 1-3 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Service designOperationsJourneyBlueprint | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |