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 Empathy Mapping | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() UX Research User Interviews |
|---|---|---|---|
Purposedifferent | 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. | 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 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 | Low | High | Low |
Timedifferent | 30–60 min | Several meetings plus preparation and analysis; total effort depends on scope | 30–60 min per interview |
Participantsdifferent | 4-8 | Evaluation team, architects, and relevant stakeholders | 1 participant per interview |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Empathy Map, Assumptions List, Research Gaps | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Interview Notes, Themes, Insight Summary |
Tagsno overlap | SynthesisQualitativeWorkshop | ArchitectureQualityRiskTradeoffsStakeholders | QualitativeResearchCustomerDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






