View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Affinity DiagrammingPersonasATAM (Architecture Tradeoff Analysis Method)Failure Mode and Effects Analysis
| Criterion | ![]() UX Research Affinity Diagramming | ![]() UX Research Personas | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Medium | High | High |
Timedifferent | 45–90 min | 1-3 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 2-6 h |
Participantsdifferent | 3-10 | Internes Team | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Persona Profiles, Needs Summary, Scenario Notes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | SynthesisQualitativeRoot cause | ResearchCustomerSynthesis | ArchitectureQualityRiskTradeoffsStakeholders | RiskQualityOperationsRoot cause |



