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 LoopStrategic, Tactical and Operational PlanningFeynman TechniqueArchitecture Decision Record
| Criterion |  Business Strategy Strategy Execution Loop |  Business Strategy Strategic, Tactical and Operational Planning |  Knowledge Modeling Feynman Technique |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 90-180 min | 20-60 min | 15-45 min |
Participantsdifferent | 5-12 | 4-12 | 1 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Plain-language Explanation, Knowledge Gaps, Study Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | ExecutionCadenceLearningGovernance | CadenceGovernanceExecution | LearningKnowledgeUnderstanding | ArchitectureRationaleDocumentationGovernance |