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 Request for Comments |  Architecture C4 Model |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 0.5-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h | 15-45 min |
Participantsdifferent | 6-12 | 3-20 Reviewer | 1-5 | 1-3 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale |
Tagsno overlap | Service designOperationsJourneyBlueprint | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance |