When a strategy fails, the postmortem usually settles on a reassuring conclusion: the strategy was sound, execution let it down. This narrative is comforting because it protects the people who authored the strategy and blames a diffuse, faceless process. It is also frequently false, or at least incomplete. Many strategies that supposedly “failed in execution” were never executable to begin with, and many others unravel not because people were incapable but because the organization was quietly arranged to defeat its own intentions. Understanding how strategies come apart in practice is the only way to build ones that hold.
The comforting myth of the execution gap
The phrase “execution gap” implies a clean handoff: a finished strategy is passed to an operations function that either delivers or fumbles. Real organizations do not work this way. A strategy that cannot be translated into specific choices by the people who receive it is not a strong strategy waiting for good execution; it is an incomplete strategy. “Become the premium player in our market” is a direction, not a strategy, and no amount of operational excellence can execute a direction. Before blaming execution, it is worth asking whether the strategy ever specified who does what differently on Monday morning.
Translation loss on the way down
A strategy is typically written by a handful of people at the top and carried out by hundreds or thousands who were never in the room. At each level of the hierarchy, the strategy is re-explained by someone who understands it slightly less than the person above them, until the frontline receives a version that has lost its reasoning and kept only its slogans. A field team told to “deepen customer relationships” without the underlying logic may reasonably interpret that as “call customers more often,” which can annoy the very accounts the strategy meant to protect. The instruction survived the journey; the intent did not. Reducing this translation loss requires leaders to carry the why down the hierarchy, not just the what.
When incentives contradict the strategy
People do what they are measured and paid to do, not what the strategy deck says they should do. This is the single most reliable cause of strategic failure, and it is almost always self-inflicted. A company announces a shift from transactional selling to long-term solutions, then leaves in place a commission plan that rewards this quarter’s booked volume. The sales force, behaving rationally, keeps selling transactions, and leadership concludes that the culture resists change. The culture is not resisting; it is responding, correctly, to the incentives it was actually given. Any strategy that survives contact with the compensation plan only if people ignore their own paychecks is not a strategy—it is a hope.
The budget and the calendar tell the truth
You can learn more about a company’s real strategy from its budget and its executives’ calendars than from its strategy document. If the stated priority receives five percent of the capital and appears on no senior leader’s calendar, it is not the priority, whatever the deck claims. Resource allocation is where strategy stops being rhetoric and becomes real, because every dollar and every hour is genuinely scarce and cannot be spent twice. A useful test after any strategy is set: pull the actual budget and a sample of leadership calendars three months later and check whether they reflect the new direction. If they look identical to the old ones, the strategy has already failed and no one has noticed yet.
Middle management is the real battlefield
Senior leaders set direction and frontline teams do the work, but middle managers are where strategies live or die. They translate intent into daily priorities, and they hold enough discretion to quietly slow anything they distrust. When a strategy stalls, middle managers are often blamed for foot-dragging, yet their reluctance usually contains real information. They are closer to customers and operations than the executives who wrote the plan, and they can see problems the strategy ignored. The productive response is to bring them in as co-authors of the parts that touch their world, not merely as recipients of a finished plan. A strategy that middle management helped shape is one they will defend rather than absorb.
Designing feedback so drift is visible
Even well-built strategies drift, because reality keeps moving after the plan is set. The defense is short, honest feedback loops that make drift visible early. This means choosing a small number of leading indicators—signals that move before the financial results do—and reviewing them on a rhythm frequent enough to allow correction. It also means creating a genuine willingness to adjust, rather than treating any deviation as a failure of loyalty to the original plan. A few practices help:
- Define, in advance, what evidence would indicate the strategy is working and what would indicate it is not.
- Review those signals on a fixed cadence, separately from the ordinary operational metrics that crowd them out.
- Give the people closest to the work a safe channel to report that the plan is not matching reality, before the gap becomes a crisis.
Execution as the continuation of strategy
The deepest fix is to stop treating strategy and execution as separate phases handled by separate people. A strategy is not finished when the document is approved; it is finished, if ever, when the organization is actually behaving differently and getting different results. Seen this way, execution is not downstream of strategy—it is strategy meeting reality and being revised by it. The organizations that get this right do not have better executors so much as strategists who never stopped paying attention after the plan was written. That sustained attention, more than any single decision, is what keeps a sound strategy from quietly coming apart.