View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Mode and Effects AnalysisAffinity DiagrammingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Operations Failure Mode and Effects Analysis |  UX Research Affinity Diagramming |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | High | Low | High |
Timedifferent | 2-6 h | 45–90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-10 | 3-10 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | FMEA Table, Risk Priority, Mitigation Actions | Theme clusters, Insight statements, Opportunity areas | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | RiskQualityOperationsRoot cause | SynthesisQualitativeRoot cause | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
