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 arc42 |  UX Research User Interviews |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 Tage | 1-2 Tage | 30–60 min per interview | 60-120 min |
Participantsdifferent | Internes Team | 1-4 | 1 participant per interview | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Architecture Document, Context View, Runtime View, Deployment View | Interview Notes, Themes, Insight Summary | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureDocumentationCommunication | QualitativeResearchCustomerDiscovery | ArchitectureCommunicationStakeholdersCanvas |