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 LoopExample MappingStrategic, Tactical and Operational Planning4Ls Retrospective
| Criterion |  Business Strategy Strategy Execution Loop |  Agile Example Mapping |  Business Strategy Strategic, Tactical and Operational Planning |  Agile 4Ls 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 30-60 min | 90-180 min | 45–75 min |
Participantsdifferent | 5-12 | 3-7 | 4-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Example Map, Acceptance Criteria, Open Questions | Planning Levels Map, Cadence Model, Planning Artifact Inventory | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ExecutionCadenceLearningGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CadenceGovernanceExecution | RetrospectiveLearningReflectionTeam |