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 |  Architecture Request for Comments |  UX Design Customer Journey Canvas |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 15-45 min |
Participantsdifferent | Internes Team | 3-20 Reviewer | 3-10 | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Customer Journey Canvas, Pain Points, Experience Opportunities | ADR File, Decision Log, Rationale |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureDecisionAsyncGovernance | JourneyCustomerService designCanvas | ArchitectureRationaleDocumentationGovernance |