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 C4 Model |  Architecture arc42 |  UX Research User Interviews |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Tage | 1-4 h | 1-2 Tage | 30–60 min per interview |
Participantsdifferent | Internes Team | 1-5 | 1-4 | 1 participant per interview |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View | Interview Notes, Themes, Insight Summary |
Tagsno overlap | ResearchCustomerSynthesis | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication | QualitativeResearchCustomerDiscovery |