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 Empathy Mapping |  UX Research Personas |
|---|---|---|---|
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 a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. | 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 | High | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30–60 min | 1-3 Tage |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 4-8 | Internes Team |
Formatdifferent | Workshop + async | Workshop | 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 | Empathy Map, Assumptions List, Research Gaps | Persona Profiles, Needs Summary, Scenario Notes |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | SynthesisQualitativeWorkshop | ResearchCustomerSynthesis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
