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 User Interviews |  UX Research Personas |  Architecture Software Architecture Canvas |
|---|---|---|---|
Purposedifferent | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 30–60 min per interview | 1-3 Tage | 1-2 h |
Participantsdifferent | 1 participant per interview | Internes Team | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Themes, Insight Summary | Persona Profiles, Needs Summary, Scenario Notes | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | QualitativeResearchCustomerDiscovery | ResearchCustomerSynthesis | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
