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 | ![]() Engineering Hypothesis-Driven Troubleshooting | ![]() Operations Gemba Walk |
|---|---|---|---|
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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | High | Medium | Low |
Timedifferent | 1-4 h | 30-240 min | 30-120 min |
Participantsdifferent | 2-8 | 1-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Contradiction Statement, Inventive Principles, Solution Concepts | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Observation Notes, Improvement Ideas |
Tagsno overlap | InnovationProblem solvingContradictionsCreativity | TroubleshootingProblem solvingDiagnosis | LeanObservationProcessOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






