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 Diagramming5 WhysATAM (Architecture Tradeoff Analysis Method)Failure Mode and Effects Analysis
| Criterion |  UX Research Affinity Diagramming |  Operations 5 Whys |  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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 | Low | High | High |
Timedifferent | 45–90 min | 15-30 min | Several meetings plus preparation and analysis; total effort depends on scope | 2-6 h |
Participantsdifferent | 3-10 | 2-6 | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Root cause notes, Countermeasures | 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 | Root causeIncidentLeanProblem solving | ArchitectureQualityRiskTradeoffsStakeholders | RiskQualityOperationsRoot cause |