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 User Interviews |  Architecture Architecture Decision Record |  UX Research Personas |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30–60 min per interview | 15-45 min | 1-3 Tage | 1-2 Tage |
Participantsdifferent | 1 participant per interview | 1-3 | Internes Team | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | ADR File, Decision Log, Rationale | Persona Profiles, Needs Summary, Scenario Notes | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | QualitativeResearchCustomerDiscovery | ArchitectureRationaleDocumentationGovernance | ResearchCustomerSynthesis | ArchitectureDocumentationCommunication |