View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations 5 Whys |  Innovation TRIZ |  Agile Example Mapping |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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 a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 15-30 min | 1-4 h | 30-60 min | 1-4 h |
Participantsdifferent | 2-6 | 2-8 | 3-7 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | Contradiction Statement, Inventive Principles, Solution Concepts | Example Map, Acceptance Criteria, Open Questions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | Root causeIncidentLeanProblem solving | InnovationProblem solvingContradictionsCreativity | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Root causeProblem solvingQualityIncident |