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 arc42 |  UX Research Affinity Diagramming |  UX Research User Interviews |  UX Research Personas |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-2 Tage | 45–90 min | 30–60 min per interview | 1-3 Tage |
Participantsdifferent | 1-4 | 3-10 | 1 participant per interview | Internes Team |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Theme clusters, Insight statements, Opportunity areas | Interview Notes, Themes, Insight Summary | Persona Profiles, Needs Summary, Scenario Notes |
Tagsno overlap | ArchitectureDocumentationCommunication | SynthesisQualitativeRoot cause | QualitativeResearchCustomerDiscovery | ResearchCustomerSynthesis |