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 Outcome-Driven Innovation | ![]() Operations Root Cause Analysis | ![]() Operations Change Analysis | ![]() Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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 | High | Medium | Medium | Low |
Timedifferent | Mehrere Wochen | 1-4 h | 45-120 min | 15-30 min |
Participantsdifferent | 2-6 researchers plus sample | 3-8 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Root cause notes, Countermeasures |
Tagsno overlap | OutcomesInnovationResearchQuantitative | Root causeProblem solvingQualityIncident | ChangeRoot causeTroubleshootingComparison | Root causeIncidentLeanProblem solving |



