Home > Perspectives > Strategy Execution > Why Strategy Execution Is a Leadership Discipline, Not a One-Time Event

Why Strategy Execution Is a Leadership Discipline, Not a One-Time Event

Watch the short film

Play Video
Why strategy execution is a leadership discipline, not a one-time event: plans are launched as moments, but execution has to be sustained.

What four bodies of research found

Donald Sull, Rebecca Homkes and Charles Sull, in Harvard Business Review, studied more than 250 companies and found that lateral coordination between functions — not vertical alignment — was where execution most reliably broke down, with only 9% of managers reporting they could rely on cross-functional colleagues all of the time. Coordination of this kind isn’t a condition that gets established once at launch; it’s continuously maintained or continuously eroding, which is itself a claim about execution being ongoing rather than a completed state.

Michael Beer and Russell Eisenstat, in what is now MIT Sloan Management Review, found that implementation barriers reinforce each other, concluding that “without transforming that barrier into a capability, none of the other barriers can be turned into capabilities either.” A capability, by definition, is something maintained over time — not a milestone reached once and left behind.

The word choice there is deliberate and worth dwelling on: Beer and Eisenstat describe the goal as transforming a barrier into a capability, not simply removing the barrier. Removal implies a one-time act — the obstacle is gone. Building a capability implies an ongoing state that has to be sustained against whatever pressures would otherwise erode it, which is a meaningfully different and more demanding standard than simply clearing a blockage once.

Larry Greiner, in Harvard Business Review, found that practices well-suited to one phase of organisational growth become the source of crisis in the next, meaning that even a well-executed plan can become mismatched to an organisation that has changed since the plan was approved — a mismatch that can only be caught by ongoing attention, not by anything decided at launch.

V. F. Ridgway, in Administrative Science Quarterly, found that the measures used to track progress can distort the behaviour meant to deliver it over time, as people gradually optimise toward the measure rather than the underlying goal — a drift that happens continuously across a plan’s lifespan, not at any single decision point.

Where they converge

None of these four studies was framed around the question of whether execution is a one-time event or an ongoing discipline. And yet each identifies a failure mode that is fundamentally continuous rather than momentary: coordination that has to be maintained, capability that has to be sustained, organisational fit that has to be periodically reassessed, and measurement that has to be periodically checked against its own distorting effects. None of these is something a leadership team gets right once, at launch, and can then set aside.

That convergence, across four separate research traditions that weren’t in conversation with each other, is more persuasive than any single study arguing the point directly would be. It suggests that treating strategy execution primarily as a launch event — significant, well-resourced, but essentially complete once the initial rollout has happened — misreads what the research, collectively, is describing. Each study points to a different mechanism, but all four mechanisms operate continuously, for as long as the strategy is meant to be in effect.

It’s worth naming what makes this convergence more than coincidence. Coordination, capability, organisational fit and measurement integrity are each, by their nature, states rather than milestones — conditions that hold or don’t hold at any given moment, rather than boxes that get ticked once. A launch event can establish the initial conditions for each of these to be strong. None of the four studies suggests a launch event can guarantee any of them will remain strong, because nothing about a single point in time controls what happens in every subsequent month the strategy remains in effect.

What remains genuinely open

What this synthesis doesn’t resolve is how much ongoing attention is actually required, or what form it should take in a given organisation — that varies enormously by context, and none of the four studies offers a formula that would generalise cleanly. It’s also worth holding the alternative honestly: it’s possible some organisations genuinely do execute well with less continuous attention than this research collectively implies, and the four studies, however consistent with each other, don’t amount to proof that every organisation needs the same degree of ongoing focus.

What does seem reasonably well supported is the more modest claim: that treating execution as complete once a plan has launched is where a meaningful share of the divergence between intended and actual results appears to originate, across several genuinely independent bodies of evidence.

Looking for your own sector? The Other Sectors page points to the closest match.

Questions worth considering

  1. At what point after launch does anyone next ask whether a strategy is still being carried out as intended — and what prompts that question?
  2. Which parts of execution depend on conditions that must be maintained month after month rather than established once?
  3. If attention to a plan fell away after the launch event, what, if anything, would reveal it?

This perspective is part of Strategy Execution.

Your team is facing similar challenges?

Solving the Problem the Last Fix Created — strategy execution
The Riddle Ledger, a brand of Zoom Riddle

Subscribe to The Riddle Ledger

Perspectives are sent as they are published, with no promotional email, and you can unsubscribe at any time.

Sources

Michael Beer and Russell A. Eisenstat, “The Silent Killers of Strategy Implementation and Learning,” Sloan Management Review (now MIT Sloan Management Review), 41(4), 2000, pp. 29–40.

Larry E. Greiner, “Evolution and Revolution as Organizations Grow,” Harvard Business Review, Vol. 50, No. 4 (July–August 1972), pp. 37–46; republished as an HBR Classic, Vol. 76, No. 3 (May–June 1998).

V. F. Ridgway, “Dysfunctional Consequences of Performance Measurements,” Administrative Science Quarterly, Vol. 1, No. 2 (September 1956), pp. 240–247.

Donald Sull, Rebecca Homkes and Charles Sull, “Why Strategy Execution Unravels — and What to Do About It,” Harvard Business Review, Vol. 93, No. 3 (March 2015), pp. 57–66.

You need a PDF version for a meeting?

Frequently Asked Questions

Because each was examining a mechanism — coordination, capability-building, organisational fit, measurement distortion — that happens to be continuous by nature, even though none of the studies set out specifically to argue that execution is an ongoing discipline. The convergence emerges from what each mechanism actually is, not from a shared starting assumption.
No — a defined launch remains useful for communication, resourcing and alignment. The point is that launch alone doesn’t account for what the research finds actually sustains or erodes execution over the following months and years.
The research doesn’t establish a universal figure, and it likely varies significantly by organisation and context — this is one of the genuinely open questions the combined evidence doesn’t resolve.
It’s possible, and the research reviewed here doesn’t rule that out. What it does suggest is that for a meaningful number of organisations, treating execution as complete at launch is where results and intentions start to diverge.
Beer and Eisenstat describe the goal as building a capability rather than simply removing a barrier. Removal implies a one-time act in which the obstacle is gone, whereas a capability is an ongoing state that has to be sustained against pressures that would otherwise erode it, which is a more demanding standard.
V. F. Ridgway’s research suggests that measures used to track progress can distort behaviour over time, as people gradually optimise toward the measure rather than the underlying goal. That drift happens continuously across a plan’s lifespan, not at any single decision point, so it is a continuous rather than momentary failure mode.
It means each is a condition that either holds or does not hold at any given moment, rather than a box ticked once. A launch event can establish strong initial conditions, but the page notes that none of the studies suggests it can keep them strong across every later month the strategy remains in effect.
The page describes the modest version as reasonably well supported: treating execution as complete once a plan has launched appears to be where a meaningful share of the divergence between intended and actual results originates. It also stresses that the four studies are not proof that every organisation needs the same degree of ongoing focus.