Every organization has a strategy document somewhere. A PowerPoint from the last offsite. A PDF from the consulting engagement. A set of priorities that leadership agreed on, announced, and then watched slowly fade into the background noise of daily operations.
The strategy wasn’t wrong. The analysis was sound. The priorities made sense. But six months later, the organization is operating more or less the same way it was before. The document exists; the change doesn’t.
This pattern is so common it’s almost expected. Research from McKinsey suggests that roughly 70% of strategic initiatives fail to achieve their objectives.1 The failure usually isn’t in the strategy itself. It’s in the space between strategic intent and operational reality.
Why Strategies Fail to Execute
Strategy documents fail for predictable reasons, and most of them have nothing to do with the quality of the strategy itself.
The strategy isn’t translated into action. A strategic priority like “improve customer experience” or “drive operational efficiency” sounds clear in a leadership meeting. But what does it mean for the person processing orders on Tuesday morning? Without translation into specific changes to processes, systems, behaviors, and metrics, strategy remains an abstraction that doesn’t touch daily work.
Nobody owns the execution. Strategy is often developed by leadership or consultants, then handed off to the organization to “implement.” But implementation isn’t anyone’s primary job. Everyone has existing responsibilities, existing priorities, existing fires to fight. Strategic initiatives become additional work layered on top of the real work, and the real work always wins.
The organization isn’t structured for it. Strategic priorities often require cross-functional coordination. Improving customer experience touches sales, support, product, operations, and IT. But the organization is structured in silos, with each function optimizing for its own metrics. The coordination required to execute cross-functional strategy doesn’t happen automatically, and without deliberate effort it doesn’t happen at all.
There’s no feedback loop. Strategy gets set annually. Execution happens (or doesn’t) over months. But there’s often no mechanism to track progress, surface obstacles, or adjust course. By the time leadership realizes the strategy isn’t executing, significant time has been lost.
Incentives don’t align. People do what they’re measured on and rewarded for. If the strategic priority is customer experience but the sales team is compensated purely on new revenue, the sales team will rationally focus on new revenue. Strategy that conflicts with incentive structures loses.
The Translation Problem
The first breakdown usually happens at translation: converting strategic priorities into operational changes.
“Improve operational efficiency” is a direction, not a plan. It doesn’t tell anyone what to do differently. Effective translation requires answering specific questions:
What processes need to change? Which systems need modification? What new capabilities are required? Who needs to behave differently, and how? What investments are necessary? What does success look like, and how will we measure it?
This translation work is often underestimated or skipped entirely. Leadership assumes the organization will figure out how to execute the strategy. The organization assumes leadership will provide more specific direction. Neither happens, and the strategy floats above the operation without connecting to it.
Good translation produces a roadmap: a sequence of specific initiatives, with defined scope, assigned ownership, allocated resources, and measurable outcomes. Without this, strategy is just aspiration.
The Ownership Problem
Even well-translated strategies fail without clear ownership.
Strategic initiatives often require work from multiple functions, but nobody has authority across functions. The VP of Sales can direct sales activities; the VP of Operations can direct operational changes; but a strategic initiative requiring both sits in organizational no-man’s-land.
This is why strategic initiatives need explicit owners: individuals with accountability for outcomes and authority (or at least influence) to marshal resources across boundaries. These owners need time allocated to the work, not just responsibility added to their existing roles. And they need leadership support when cross-functional coordination gets difficult.
Without ownership, strategic initiatives become everyone’s second priority and no one’s first. They progress when people have spare capacity (rarely) and stall when they don’t (usually).
The Feedback Problem
Strategy isn’t a one-time decision. It’s a hypothesis about what will work, and hypotheses need testing.
The market changes. Competitors respond. Initial assumptions prove wrong. Execution surfaces obstacles that weren’t visible from the strategy level. Effective strategy requires feedback loops: mechanisms to track progress, surface problems, and adjust course.
This means regular reviews that go beyond status updates. Not “are we on schedule?” but “is this working? What are we learning? What needs to change?” It means creating psychological safety to report problems early rather than hiding them until they’re catastrophic. It means leadership that’s willing to adjust strategy based on execution realities rather than insisting on the original plan.
Organizations that execute well treat strategy as a living process, not a fixed document. They expect to learn and adapt. They build in the mechanisms to do so.
Bridging the Gap
Closing the execution gap requires deliberate effort at each stage where strategies typically break down.
Translate explicitly. Don’t assume the organization knows how to operationalize strategic priorities. Invest the time to convert direction into specific initiatives with defined scope, success criteria, and resource requirements.
Assign ownership clearly. Every strategic initiative needs an owner with accountability for outcomes. That owner needs time, resources, and authority commensurate with the scope of the initiative.
Resource realistically. Strategic initiatives compete for resources with ongoing operations. If you’re not willing to reallocate resources or add capacity, you’re not serious about the initiative. Strategies that are “in addition to” existing workloads rarely execute.
Align incentives. Review compensation structures, performance metrics, and promotion criteria in light of strategic priorities. If the incentives point in a different direction than the strategy, change the incentives or change the strategy.
Build feedback loops. Establish regular reviews focused on learning, not just reporting. Create mechanisms to surface obstacles early. Be willing to adjust based on what you learn.
Lead visibly. Strategic priorities that leadership mentions once and never revisits signal that they’re not actually priorities. Consistent attention from leadership (asking about progress, removing obstacles, celebrating wins, addressing failures) communicates that execution matters.
The Document Isn’t the Work
A strategy document represents decisions made. It’s the output of analysis and deliberation: valuable work, but not the work that creates change.
The work that creates change happens after the document: the translation, the ownership, the resource allocation, the feedback, the adjustment, the sustained attention over months and years. Organizations that execute well invest as much effort in this post-document work as they do in developing the strategy itself.
Strategy without execution is just a document. Execution without strategy is just activity. The organizations that pull ahead do both, and they understand that the connection between them requires deliberate, sustained effort.
Citations
1 McKinsey & Company, "How to beat the transformation odds," 2015; updated findings in "The State of Organizations 2023."