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 Opportunity Interview |  Engineering Failure Scenario Analysis |  Product Discovery Opportunity Solution Tree |
|---|---|---|---|
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. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 30-60 min je Interview | 1-3 h | 1-2 h Setup, laufend |
Participantsdifferent | 5-12 Interviews | 3-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | FailureResilienceRisk | DiscoveryOutcomesExperimentsOpportunity |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
