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 LoopDomain StorytellingGemba WalkStrategic, Tactical and Operational Planning
| Criterion |  Business Strategy Strategy Execution Loop |  Knowledge Modeling Domain Storytelling |  Operations Gemba Walk |  Business Strategy Strategic, Tactical and Operational Planning |
|---|---|---|---|---|
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. | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 1-2 h | 30-120 min | 90-180 min |
Participantsdifferent | 5-12 | 2-8 | 2-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Domain Story, Glossary Notes, Process Narrative | Observation Notes, Improvement Ideas | Planning Levels Map, Cadence Model, Planning Artifact Inventory |
Tagsno overlap | ExecutionCadenceLearningGovernance | KnowledgeDomain-Driven DesignProcess | LeanObservationProcessOperations | CadenceGovernanceExecution |