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 Map | ![]() Business Strategy Strategy Execution Loop | ![]() Decision Making Force Field Analysis |
|---|---|---|---|
Purposedifferent | A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 2-4 h workshop plus review | Initial 3-6 h, then monthly or quarterly reviews | 45-90 min |
Participantsdifferent | 4-10 | 5-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Strategy Map, Objective Set, Cause-Effect Hypotheses | Execution Loop, Review Cadence, Strategic Learning Log | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | AlignmentExecutionGoalsCausality | ExecutionCadenceLearningGovernance | ChangeDecisionStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






