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 |  Agile Specification by Example |  Operations Kepner-Tregoe |  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. | 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. | 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. | 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 | Medium | High | Medium |
Timedifferent | 15-30 min | 60-90 min pro Feature | 2-8 h | 1-4 h |
Participantsdifferent | 2-6 | 3-6 | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | Example Table, Acceptance Tests | Problem Analysis, Decision Analysis, Risk Plan | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | Root causeIncidentLeanProblem solving | AgileRequirementsExamplesBehavior-Driven Development | Problem solvingRoot causeDecisionOperations | Root causeProblem solvingQualityIncident |