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 Affinity Diagramming |
|---|---|---|---|
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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 Tage | 45–90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | Internes Team | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
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 | Theme clusters, Insight statements, Opportunity areas |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ResearchCustomerSynthesis | SynthesisQualitativeRoot cause |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
