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 SAAM (Software Architecture Analysis Method) |  Product Discovery Opportunity Solution Tree |  Product Discovery Opportunity Interview |
|---|---|---|---|
Purposedifferent | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. | 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 | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 1-2 h Setup, laufend | 30-60 min je Interview |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-6 | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Opportunity Solution Tree, Experiment Backlog, Learning Log | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | DiscoveryOutcomesExperimentsOpportunity | DiscoveryInterviewsOpportunityCustomer |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
