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 Opportunity Interview |
|---|---|---|
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 opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. |
Complexitydifferent | High | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min je Interview |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 5-12 Interviews |
Formatsame | 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 | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | DiscoveryInterviewsOpportunityCustomer |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.





