When Strategy Fails: Is It the Strategy, the Execution, or Something Else?

There's a point in almost every planning cycle where everything appears to be crystal clear. The priorities are locked in, the roadmap makes sense, the leadership team is aligned, and the final deck is ready to go.

Then everyone heads back to their desks, and that's usually where things slowly and quietly start to fray.

One priority quietly multiplies into five. Cross-functional decisions stall. Different departments walk away with entirely different — and sometimes conflicting — interpretations of the goal. A critical initiative relies on someone who is already stretched to the limit, and recurring status meetings can seem to be going nowhere because they often can be held up on the exact same roadblocks.

Eventually, after all the time and resources invested in the process, leadership is left asking the inevitable question: Why isn't this strategy working?

Experience has taught me that asking whether the strategy is working may not always be the right place to start.

Sometimes, the strategy itself is the problem. Other times, execution is genuinely failing. Making that distinction matters, because it's easy to point fingers at execution when a strategy simply wasn't rigorous enough about trade-offs or hard choices from the start.

This is why I look at strategy and execution as a single, connected ecosystem rather than two distinct silos:

• Strategy sets the direction.
• Execution translates that direction into real-world choices, clear ownership, and momentum.
• People, processes, and systems bring the operational muscle required to move the work forward.
• Performance metrics tell you whether any of the above is actually moving the needle.

Like a chain, when one link snaps, the whole organization feels it. Research on the strategy-execution gap points to fragmented leadership, rigid organizational structures, cultural resistance, technology limitations and weak performance measurement. These are the messy ones.

That's why I pause when I hear someone say, “It just wasn't executed properly.”

Well, maybe. But exactly where did it fall apart?

Look at What Happens After the Meeting

The real clues are almost always hidden in the day-to-day aftermath:

• Can people actually articulate the core priorities without looking at a slide?
• Do they understand what those priorities mean for their own work?
• Are decisions being made at the right level or are they constantly bubbling up to the top?
• Does everyone know who definitively owns what?
• Are budgets and headcount well-aligned with what leadership says matters most?
• Can leadership spot when a project is going off the rails before it hits a crisis?
• Most importantly: is the organization learning and adapting as market realities shift?

Those questions can tell you far more about what is actually happening in the business than another high-level offsite.

The Gap is Usually in the Connections

I've spent the bulk of my career living in the messy space between high-level strategy and getting things across the finish line. That experience has made me less interested in strategy as a document and much more interested in what happens to strategy once it enters an organization — because that's where value is either created or lost.

The work isn't finished when the strategy is approved and gets a rubber stamp. In many ways, that's where it begins.

If strategy and results aren't lining up, don't immediately assume you need a new strategy or a harder push on execution. Step back first and find the weakest link in the connection. That's usually where the real work begins.