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 ATAM (Architecture Tradeoff 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. | 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. | 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 | Several meetings plus preparation and analysis; total effort depends on scope | 60-120 min |
Participantsdifferent | 5-12 Interviews | Evaluation team, architects, and relevant stakeholders | 3-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Opportunity Score Table, Top Outcomes |
Tagsno overlap | CustomerOutcomesNeeds | ArchitectureQualityRiskTradeoffsStakeholders | PrioritizationDiscoveryOutcomesNeeds |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
