View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordStrategy Execution LoopRoot Cause Tree AnalysisRoot Cause Analysis
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Business Strategy Strategy Execution Loop | ![]() Operations Root Cause Tree Analysis | ![]() Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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-45 min | Initial 3-6 h, then monthly or quarterly reviews | 1-3 h | 1-4 h |
Participantsdifferent | 1-3 | 5-12 | 2-8 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Execution Loop, Review Cadence, Strategic Learning Log | Cause Tree, Evidence Notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ExecutionCadenceLearningGovernance | Root causeTreeIncidentQuality | Root causeProblem solvingQualityIncident |



