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 |  Operations A3 Problem Solving |  Product Discovery Opportunity Solution Tree |  Operations 5 Whys |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 30-60 min je Interview | 45-90 min | 1-2 h Setup, laufend | 15-30 min |
Participantsdifferent | 5-12 Interviews | 2-5 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | A3 Report, Action Plan, Root Cause Analysis | Opportunity Solution Tree, Experiment Backlog, Learning Log | Root cause notes, Countermeasures |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | LeanProblem solvingCoachingOperations | DiscoveryOutcomesExperimentsOpportunity | Root causeIncidentLeanProblem solving |