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) |  Architecture Risk Storming |  Product Discovery Problem 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. |
Complexitydifferent | High | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min | 30-60 min je Interview |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 4-12 | 5-12 Interviews |
Formatdifferent | Workshop + async | Workshop | 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 | Annotated Diagram, Prioritized Risk List, Action Backlog | Problem Evidence, Risk Notes, Customer Segments |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | RiskArchitectureWorkshopValidation | DiscoveryInterviewsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
