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 Personas |  UX Research Customer Journey Mapping |  Architecture Architecture Decision Record |  UX Design Service Blueprinting |
|---|---|---|---|---|
Purposedifferent | When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | 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 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 Tage | 2-4 h | 15-45 min | 0.5-2 Tage |
Participantsdifferent | Internes Team | 4-10 | 1-3 | 6-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Journey Map, Pain-point List, Opportunity Backlog | ADR File, Decision Log, Rationale | Service Blueprint, Fail Points, Ownership Map |
Tagsno overlap | ResearchCustomerSynthesis | JourneyServiceService design | ArchitectureRationaleDocumentationGovernance | Service designOperationsJourneyBlueprint |