View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Feynman TechniqueStrategic, Tactical and Operational PlanningStrategy Execution LoopArchitecture Decision Record
| Criterion | ![]() Knowledge Modeling Feynman Technique | ![]() Business Strategy Strategic, Tactical and Operational Planning | ![]() Business Strategy Strategy Execution Loop | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 20-60 min | 90-180 min | Initial 3-6 h, then monthly or quarterly reviews | 15-45 min |
Participantsdifferent | 1 | 4-12 | 5-12 | 1-3 |
Formatdifferent | Async | Workshop | Workshop + async | Async |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Planning Levels Map, Cadence Model, Planning Artifact Inventory | Execution Loop, Review Cadence, Strategic Learning Log | ADR File, Decision Log, Rationale |
Tagsno overlap | LearningKnowledgeUnderstanding | CadenceGovernanceExecution | ExecutionCadenceLearningGovernance | ArchitectureRationaleDocumentationGovernance |



