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 |  Agile Start Stop Continue |  Agile Sprint Retrospective |
|---|---|---|---|---|
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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 20-60 min | 30-60 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 5-12 | 1 | 3-12 | Scrum Team |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Plain-language Explanation, Knowledge Gaps, Study Notes | Start Stop Continue Board, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | ExecutionCadenceLearningGovernance | LearningKnowledgeUnderstanding | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementLearning |