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 |  Operations 5 Whys |  Agile Specification by Example |
|---|---|---|---|
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. | 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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | High | Low | Medium |
Timedifferent | 1-4 h | 15-30 min | 60-90 min pro Feature |
Participantsdifferent | 2-8 | 2-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Contradiction Statement, Inventive Principles, Solution Concepts | Root cause notes, Countermeasures | Example Table, Acceptance Tests |
Tagsno overlap | InnovationProblem solvingContradictionsCreativity | Root causeIncidentLeanProblem solving | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
