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 |  Knowledge Modeling Feynman Technique |  Architecture Architecture Decision Record |  Knowledge Modeling IBIS |
|---|---|---|---|---|
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. | 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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 20-60 min | 15-45 min | 1-3 h |
Participantsdifferent | 5-12 | 1 | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Plain-language Explanation, Knowledge Gaps, Study Notes | ADR File, Decision Log, Rationale | Issue Map, Positions, Argument Notes |
Tagsno overlap | ExecutionCadenceLearningGovernance | LearningKnowledgeUnderstanding | ArchitectureRationaleDocumentationGovernance | RationaleKnowledgeDecision |