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 Jobs to Be Done |  Architecture SAAM (Software Architecture Analysis Method) |  Product Discovery Opportunity Scoring |
|---|---|---|---|
Purposedifferent | When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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 opportunities need ranking by their effect, it makes importance and satisfaction directly comparable. It separates problem, assumption, solution, and evidence. The result is captured as an opportunity-score table and top outcomes. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 Wochen | Preparation, scenario analysis, and findings review; effort depends on scope | 60-120 min |
Participantsdifferent | 5-12 Interviews | Architecture experts and stakeholders for scenarios and weighting | 3-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | 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 Score Table, Top Outcomes |
Tagsno overlap | CustomerOutcomesNeeds | ArchitectureChangeAnalysisComparisonQuality | PrioritizationDiscoveryOutcomesNeeds |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
