View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Strategy RICE Scoring |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Fishbone Diagram |  Decision Making Pareto Analysis |
|---|---|---|---|---|
Purposedifferent | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | 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 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. | In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 60-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 30-60 min |
Participantsdifferent | 2-10 | Evaluation team, architects, and relevant stakeholders | 2-8 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RICE Scores, Ranked List, Assumption Log | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Fishbone Diagram, Cause Categories, Investigation Backlog | Pareto Chart, Top Causes, Focus List |
Tagsno overlap | PrioritizationScoringRoadmapTradeoffs | ArchitectureQualityRiskTradeoffsStakeholders | Root causeQualityOperations | PrioritizationQualityFocusRoot cause |