View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation TRIZ |  Product Discovery Outcome-Driven Innovation |  Operations Root Cause Tree Analysis |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | 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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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 | 1-4 h | Mehrere Wochen | 1-3 h | 15-30 min |
Participantsdifferent | 2-8 | 2-6 researchers plus sample | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Contradiction Statement, Inventive Principles, Solution Concepts | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Cause Tree, Evidence Notes, Countermeasures | Root cause notes, Countermeasures |
Tagsno overlap | InnovationProblem solvingContradictionsCreativity | OutcomesInnovationResearchQuantitative | Root causeTreeIncidentQuality | Root causeIncidentLeanProblem solving |