View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Fishbone Diagram |  UX Research Tree Testing |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
Purposedifferent | 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. | When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination. | 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 | Low | Medium | High |
Timedifferent | 30-60 min | 1-2 Tage | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | Based on research question | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Findability Metrics, Path Analysis, Revised IA | 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 | Root causeQualityOperations | Information architectureNavigationFindability | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
