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 ATAM (Architecture Tradeoff Analysis Method) |  UX Research Personas |  UX Research User Interviews |
|---|---|---|---|
Purposedifferent | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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 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 | High | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 Tage | 30–60 min per interview |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | Internes Team | 1 participant per interview |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Persona Profiles, Needs Summary, Scenario Notes | Interview Notes, Themes, Insight Summary |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ResearchCustomerSynthesis | QualitativeResearchCustomerDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
