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 |  Decision Making Argument Mapping |  UX Research Customer Journey Mapping |
|---|---|---|---|---|
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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | 0.5-2 Tage | 15-45 min | 1-3 h | 2-4 h |
Participantsdifferent | 6-12 | 1-3 | 1-8 | 4-10 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | ADR File, Decision Log, Rationale | Argument Map, Evidence Gaps, Decision Rationale | Journey Map, Pain-point List, Opportunity Backlog |
Tagsno overlap | Service designOperationsJourneyBlueprint | ArchitectureRationaleDocumentationGovernance | SensemakingDecisionRationale | JourneyServiceService design |