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 |  UX Research User Interviews |  UX Research Personas |  UX Research Affinity Diagramming |
|---|---|---|---|---|
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. | 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. | 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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 30–60 min per interview | 1-3 Tage | 45–90 min |
Participantsdifferent | 1-3 | 1 participant per interview | Internes Team | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Interview Notes, Themes, Insight Summary | Persona Profiles, Needs Summary, Scenario Notes | Theme clusters, Insight statements, Opportunity areas |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | QualitativeResearchCustomerDiscovery | ResearchCustomerSynthesis | SynthesisQualitativeRoot cause |