View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategy Execution LoopArchitecture Decision RecordRoot Cause AnalysisStrategic, Tactical and Operational Planning
| Criterion |  Business Strategy Strategy Execution Loop |  Architecture Architecture Decision Record |  Operations Root Cause Analysis |  Business Strategy Strategic, Tactical and Operational Planning |
|---|---|---|---|---|
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. | 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. | 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. | It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 15-45 min | 1-4 h | 90-180 min |
Participantsdifferent | 5-12 | 1-3 | 3-8 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | ADR File, Decision Log, Rationale | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Planning Levels Map, Cadence Model, Planning Artifact Inventory |
Tagsno overlap | ExecutionCadenceLearningGovernance | ArchitectureRationaleDocumentationGovernance | Root causeProblem solvingQualityIncident | CadenceGovernanceExecution |