Strategy implementation

Fewer than one in three strategically important initiatives is executed as planned — McKinsey's research, and the reason this step exists. The root causes are almost never the strategy itself. They are execution failures: misaligned structures, wrong metrics, change resistance, resources that don't match priorities.

By this point you have the environment mapped, the portfolio decided and a competitive position chosen. None of it matters until it is translated into action — and the translation is where strategies die. The tools in this step exist to prevent each of the named failure modes: the 7-S framework catches misalignment, the balanced scorecard catches wrong metrics, Kotter's model manages resistance, and structure choice puts decisions where the strategy needs them.

The 7-S framework names seven internal elements that must point in the same direction for strategy to succeed. If even one is misaligned, execution suffers. Its value is precisely that it forces attention to the full system — not just structure and budget, but culture, leadership style and shared values.

Watch it diagnose a real failure. A Zambian bank pursues a digital-first strategy to reach unbanked customers by mobile. The strategy is clear — but decisions stay centralised in Lusaka under a hierarchical branch structure (Structure misaligned), technology hiring is squeezed by grade-band pay built for branch roles (Staff misaligned), and bonuses still reward in-branch transactions rather than mobile onboarding (Systems misaligned). The strategy will fail — not because the idea is wrong, but because the elements are pulling against it. The fix is never "communicate the strategy harder"; it is realigning the specific elements that contradict it.

A strategy is a hypothesis: if we do X, then Y will result. The balanced scorecard turns the hypothesis into measurable targets across four perspectives, so you can see whether the strategy is working — and intervene before the financial results deteriorate.

The power is in the cause-and-effect chain running up the table: invest in learning and growth (train people) → internal processes improve (serve faster, fewer errors) → customer outcomes improve (higher satisfaction, lower churn) → financial results improve. Without the chain, a company can hit this year's financial targets by destroying the capabilities that generate next year's.

In practice the four numbers are small and specific. A Zambian telecoms company pursuing retention might track ZMW revenue per subscriber and churn cost avoided (financial), net promoter score and complaint resolution rate (customer), time-to-resolve a service fault (internal process), and the share of frontline staff trained on the new systems (learning and growth). Reviewed monthly, those four tell a more complete strategic story than revenue alone ever could.

Strategy is ultimately people changing their behaviour. If the organisation has worked one way for years, a new strategy means breaking old patterns and building new ones — and this is where most implementation efforts fail, because people resist change they don't understand the necessity of.

Kotter's research distilled the sequence that separates successful transformations from failures into eight steps — and the cost of skipping each is specific.

Budget for it. Realistic implementation plans put 30–40% of effort into change management. A new CEO arriving at a large parastatal with a transformation mandate spends the first 90 days on Kotter's steps 1–3 — building the case for urgency, recruiting a coalition of credible senior sponsors, and forming a vision people can picture — because launching restructuring announcements without them is how transformations produce paper change and quiet reversion.

Chandler's principle — structure should follow strategy — sounds obvious and is violated constantly. Organisations redesign the strategy and then execute it through structures built for a different purpose. The result is friction: decisions made in the wrong place, accountability diffused, coordination failures. Choosing the structure is a strategic decision, not an HR exercise.

The fit is readable from the strategy. A Zambian fintech pursuing cost leadership in digital payments suits a functional structure — centralised technology, lean operations, minimum overhead. A pharmaceutical company with several product categories suits a divisional structure so each category can run its own market approach. And the first symptom of misalignment is always the same: decisions keep escalating to levels that shouldn't need to make them.

Implementation is not a project with a completion date; it is an ongoing loop of monitoring, comparing actuals to targets, diagnosing gaps and adapting. Strategic control differs from operational control in the question it asks: operational control asks "are we executing efficiently?" — strategic control asks "is the strategy itself still valid?"

• Premise control — monitor the assumptions behind the strategy; if the PESTEL factors that justified it change materially, the strategy may need revision.
• Implementation control — track whether milestones are hit and resources deployed as planned.
• Strategic surveillance — broad monitoring of the environment for unexpected developments.
• Special alert control — pre-defined response protocols for sudden crises: a rival's acquisition, a regulatory change, a supply disruption.

The four types earn their keep in a live case. First Quantum's strategy for Kansanshi assumed copper at USD 8,500 per tonne; the price falls to USD 6,200. Premise control is the type that catches it — the strategy's core assumption has broken, which triggers a fundamental review: which projects still clear their hurdle rates at the new price, what cost position is needed to ride out the trough, and at what price level the mine plan itself changes. Implementation control would only report that milestones are on schedule — on a strategy whose premise no longer holds. Knowing which control type catches which failure is what the exam tests.