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 Fault Tree Analysis |  Operations Family Tree 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. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | 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 | High | Medium | Low |
Timedifferent | Mehrere Wochen | 2-6 h | 2-4 h | 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 | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Family Tree Diagram, Pattern Notes, Systemic Measures | Root cause notes, Countermeasures |
Tagsno overlap | OutcomesInnovationResearchQuantitative | RiskRoot causeSafety | Root causePatternsIncidentSystemic | Root causeIncidentLeanProblem solving |