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 Research Personas |  Architecture arc42 |  UX Design Customer Journey Canvas |
|---|---|---|---|---|
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 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | 1-3 Tage | 1-2 Tage | 1-3 h |
Participantsdifferent | 4-10 | Internes Team | 1-4 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | Persona Profiles, Needs Summary, Scenario Notes | Architecture Document, Context View, Runtime View, Deployment View | Customer Journey Canvas, Pain Points, Experience Opportunities |
Tagsno overlap | JourneyServiceService design | ResearchCustomerSynthesis | ArchitectureDocumentationCommunication | JourneyCustomerService designCanvas |