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 Discovery Problem Interview |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Trade-off Analysis |
|---|---|---|---|
Purposedifferent | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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. | With limited resources, quality, speed, cost, and risk almost always compete with each other. Trade-off Analysis makes these tensions explicit and prevents decisions from producing hidden side effects. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 30-60 min je Interview | Several meetings plus preparation and analysis; total effort depends on scope | 45-120 min |
Participantsdifferent | 5-12 Interviews | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Trade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides |
Tagsno overlap | DiscoveryInterviewsValidation | ArchitectureQualityRiskTradeoffsStakeholders | TradeoffsDecisionCriteriaOptions |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
