View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)User InterviewsFishbone DiagramFailure Mode and Effects Analysis
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  UX Research User Interviews |  Operations Fishbone Diagram |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
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 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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 | High | Low | Low | High |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30–60 min per interview | 30-60 min | 2-6 h |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1 participant per interview | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | 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 | Interview Notes, Themes, Insight Summary | Fishbone Diagram, Cause Categories, Investigation Backlog | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | QualitativeResearchCustomerDiscovery | Root causeQualityOperations | RiskQualityOperationsRoot cause |