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 Architecture Decision Record |  Architecture Request for Comments |
|---|---|---|---|
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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | High | Low | Medium |
Timedifferent | 0.5-2 Tage | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 6-12 | 1-3 | 3-20 Reviewer |
Formatdifferent | Workshop | Async | Async |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | Service designOperationsJourneyBlueprint | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
