View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:PersonasATAM (Architecture Tradeoff Analysis Method)Customer Journey CanvasCustomer Journey Mapping
| Criterion |  UX Research Personas |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  UX Design Customer Journey Canvas |  UX Research Customer Journey Mapping |
|---|---|---|---|---|
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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. | 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 | Medium | High | Medium | Medium |
Timedifferent | 1-3 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 2-4 h |
Participantsdifferent | Internes Team | Evaluation team, architects, and relevant stakeholders | 3-10 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Customer Journey Canvas, Pain Points, Experience Opportunities | Journey Map, Pain-point List, Opportunity Backlog |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureQualityRiskTradeoffsStakeholders | JourneyCustomerService designCanvas | JourneyServiceService design |