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 Problem Interview |  Product Discovery Concierge MVP |  Operations 5 Whys |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. | 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-60 min je Interview | 1-4 Wochen | 15-30 min | 1-4 h |
Participantsdifferent | 5-12 Interviews | 3-10 Kunden | 2-6 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Concierge Learnings, Service Blueprint, MVP Risks | Root cause notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | DiscoveryInterviewsValidation | MVPValidationServiceDiscovery | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident |