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 Research Customer Journey Mapping |  UX Design Service Blueprinting |  Architecture Request for Comments |
|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 2-4 h | 0.5-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 4-10 | 6-12 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop | Async |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Service Blueprint, Fail Points, Ownership Map | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | JourneyServiceService design | Service designOperationsJourneyBlueprint | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
