View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Service BlueprintingRequest for CommentsArchitecture Decision RecordCustomer Journey Canvas
| Criterion |  UX Design Service Blueprinting |  Architecture Request for Comments |  Architecture Architecture Decision Record |  UX Design Customer Journey Canvas |
|---|---|---|---|---|
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. | 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. | 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 | High | Medium | Low | Medium |
Timedifferent | 0.5-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min | 1-3 h |
Participantsdifferent | 6-12 | 3-20 Reviewer | 1-3 | 3-10 |
Formatdifferent | Workshop | Async | Async | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | Service designOperationsJourneyBlueprint | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance | JourneyCustomerService designCanvas |