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 Kepner-Tregoe |  Operations Failure Mode and Effects 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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 | High | Low |
Timedifferent | Mehrere Wochen | 2-8 h | 2-6 h | 15-30 min |
Participantsdifferent | 2-6 researchers plus sample | 2-8 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Problem Analysis, Decision Analysis, Risk Plan | FMEA Table, Risk Priority, Mitigation Actions | Root cause notes, Countermeasures |
Tagsno overlap | OutcomesInnovationResearchQuantitative | Problem solvingRoot causeDecisionOperations | RiskQualityOperationsRoot cause | Root causeIncidentLeanProblem solving |