View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Opportunity InterviewATAM (Architecture Tradeoff Analysis Method)Software Architecture Canvas
| Criterion |  Product Discovery Opportunity Interview |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Software Architecture Canvas |
|---|---|---|---|
Purposedifferent | 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. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 30-60 min je Interview | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h |
Participantsdifferent | 5-12 Interviews | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | ArchitectureQualityRiskTradeoffsStakeholders | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
