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 |  Operations PDCA Cycle |  Product Discovery Opportunity Solution Tree |  Product Discovery Opportunity Interview |
|---|---|---|---|---|
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. | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | 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 | Medium | Low | Medium | Medium |
Timedifferent | 1-3 Wochen | 1 h bis mehrere Wochen | 1-2 h Setup, laufend | 30-60 min je Interview |
Participantsdifferent | 5-12 Interviews | 1-8 | 2-6 | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Opportunity Solution Tree, Experiment Backlog, Learning Log | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | CustomerOutcomesNeeds | Continuous improvementLeanExperiments | DiscoveryOutcomesExperimentsOpportunity | DiscoveryInterviewsOpportunityCustomer |