Why strategic plans never leave the drawing board

Every year, sometime between September and December, executive teams meet to review strategy. They leave with a polished presentation, half a dozen objectives, and a list of initiatives. By March, half the initiatives have lost priority to operational emergencies. By June, few managers can say what the objectives were.

This pattern is well known and documented. What varies from company to company is exactly where the chain breaks.

The size of the loss

Mankins and Steele (2005) surveyed 197 large companies and concluded that, on average, they realized only 63% of the financial value their own strategic plans projected. The authors listed the causes executives cited most: inadequate or unavailable resources, poorly communicated strategy, poorly defined required actions, unclear accountability, and insufficient performance monitoring.

Ten years later, Sull, Homkes, and Sull (2015) surveyed thousands of managers in hundreds of companies. One of the most cited results: only 55% of middle managers could name even one of their company's top five priorities. The authors also showed that vertical coordination worked reasonably well, with most managers saying they could rely on their bosses and direct reports, while coordination across units was the weak link: only 9% said they could always rely on colleagues in other functions and units.

Five breaking points

1. The plan is not a strategy. Rumelt (2011) describes the kernel of a good strategy with three elements: a diagnosis that explains the challenge, a guiding policy that defines the approach, and coherent actions. Many plans skip the diagnosis and jump straight to targets. "Grow 15% a year" is an aspiration, not a strategy. Without explaining what prevents that growth today, initiatives become a wish list.

2. Too many priorities. When everything is a priority, middle management chooses on its own what to do, and each area chooses differently. We often find plans with more than twenty "strategic" initiatives for a 500-person company.

3. Disconnected budget. The plan is approved in one meeting and the budget in another, under a different logic. Kaplan and Norton (2008) devoted a significant part of The Execution Premium to this problem, proposing a system that links strategic planning, operational planning, and budgeting in a single cycle.

4. Weak horizontal coordination. The Sull data point is telling. Strategic initiatives almost always depend on more than one area, while management rituals tend to be vertical: each director reviews their indicators with their own team. Nobody reviews the dependencies.

5. Reviews as accountability rather than learning. Follow-up meetings that just color indicators green, yellow, and red do not change decisions. When an objective has been red for three quarters and nothing has been reallocated, the review has become a ritual.

How to find where your chain breaks

Symptom	Likely breaking point	Question for the executive team
Managers cannot name the priorities	Too many priorities or weak communication	How many priorities do we really have? Do they fit on one slide?
Initiatives approved without budget or people	Disconnected budget	Which strategic initiative received resources taken from another area?
Projects stuck at interfaces	Horizontal coordination	Who arbitrates conflicts between areas on shared initiatives?
Ambitious targets with no explanation of the obstacle	No diagnosis	What, concretely, prevents the result today?
Indicators red for several cycles	Reviews without consequence	What was the last reallocation decision made in a review?

What works in practice

In our experience with mid-sized companies, three adjustments have more effect than switching planning methodology.

The first is limiting corporate priorities to a number people can remember, somewhere between three and five, and writing a one-paragraph diagnosis for each. The exercise forces the executive team to discuss causes, not just targets.

The second is creating a short monthly forum, separate from area reviews, dedicated only to initiatives that cross boundaries. The agenda has one item: what is stuck at an interface and who decides.

The third is tying approval of each strategic initiative to explicit resources in the budget, naming where they come from. An initiative that takes nothing from anywhere is rarely a real priority.

Assessing the maturity of the planning process, not just the content of the plan, is usually the most useful starting point. It shows whether the problem lies in formulation, cascading, allocation, or follow-up, and keeps the company from spending the next cycle redoing the part that already worked.