View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Architecture arc42 |  UX Research Personas |  UX Research User Interviews |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 1-2 Tage | 1-3 Tage | 30–60 min per interview |
Participantsdifferent | 1-3 | 1-4 | Internes Team | 1 participant per interview |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View | Persona Profiles, Needs Summary, Scenario Notes | Interview Notes, Themes, Insight Summary |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication | ResearchCustomerSynthesis | QualitativeResearchCustomerDiscovery |