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 arc42 |  Architecture Request for Comments |  Architecture C4 Model |
|---|---|---|---|---|
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. | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 | High | Low | Medium | Low |
Timedifferent | 0.5-2 Tage | 1-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h |
Participantsdifferent | 6-12 | 1-4 | 3-20 Reviewer | 1-5 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Architecture Document, Context View, Runtime View, Deployment View | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | Service designOperationsJourneyBlueprint | ArchitectureDocumentationCommunication | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationVisualization |