View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Execution Loop |  Operations Root Cause Analysis |  Architecture Architecture Decision Record |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 1-4 h | 15-45 min | 15-30 min |
Participantsdifferent | 5-12 | 3-8 | 1-3 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | ADR File, Decision Log, Rationale | Root cause notes, Countermeasures |
Tagsno overlap | ExecutionCadenceLearningGovernance | Root causeProblem solvingQualityIncident | ArchitectureRationaleDocumentationGovernance | Root causeIncidentLeanProblem solving |