View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Outcome-Driven Innovation |  Operations Root Cause 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. | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | High | High | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | Mehrere Wochen | 1-4 h |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-6 researchers plus sample | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | OutcomesInnovationResearchQuantitative | Root causeProblem solvingQualityIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
