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 Research User Interviews |  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 teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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 | Low | Low |
Timedifferent | 1-3 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 30–60 min per interview | 15-45 min |
Participantsdifferent | Internes Team | 3-20 Reviewer | 1 participant per interview | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Interview Notes, Themes, Insight Summary | ADR File, Decision Log, Rationale |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureDecisionAsyncGovernance | QualitativeResearchCustomerDiscovery | ArchitectureRationaleDocumentationGovernance |