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 |  Business Strategy Strategy Execution Loop |  Operations Family Tree Analysis |  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. | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | 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 | Medium | Medium |
Timedifferent | 15-30 min | Initial 3-6 h, then monthly or quarterly reviews | 2-4 h | 1-4 h |
Participantsdifferent | 2-6 | 5-12 | 2-6 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | Execution Loop, Review Cadence, Strategic Learning Log | Family Tree Diagram, Pattern Notes, Systemic Measures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | Root causeIncidentLeanProblem solving | ExecutionCadenceLearningGovernance | Root causePatternsIncidentSystemic | Root causeProblem solvingQualityIncident |