View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordService BlueprintingCustomer Journey MappingRequest for Comments
| Criterion |  Architecture Architecture Decision Record |  UX Design Service Blueprinting |  UX Research Customer Journey Mapping |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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 service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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 | Low | High | Medium | Medium |
Timedifferent | 15-45 min | 0.5-2 Tage | 2-4 h | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 6-12 | 4-10 | 3-20 Reviewer |
Formatdifferent | Async | Workshop | Workshop | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Service Blueprint, Fail Points, Ownership Map | Journey Map, Pain-point List, Opportunity Backlog | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Service designOperationsJourneyBlueprint | JourneyServiceService design | ArchitectureDecisionAsyncGovernance |