Why Execution Fails (Even When Strategy Is Clear)

Some people run the business.

I change businesses.

I’ve spent 25 years solving complex problems—leading and advising on major transformation efforts - and one thing still puzzles me:

How is this still a problem?

We already know how to solve this.

There are proven practices. Established playbooks. Principles - undeniable truths - that work.

And yet…

Projects go red. Programs stall. “Transformation” efforts quietly fail - most of the time.

The Uncomfortable Truth

Let’s call it directly:

Execution isn’t failing.

Your system is producing exactly what it’s designed to produce.

That’s the uncomfortable truth most leadership teams avoid - because it shifts the problem from execution… to leadership.

Because if execution isn’t the problem, then the problem is the system you’ve built to:

• Align priorities

• Make decisions

• Drive accountability

In other words - how you actually move toward your vision.

It’s Not Strategy. It’s Not Capability. It’s Not Effort.

Most organizations I work with don’t lack:

• Strategy

• Capability

• Effort

What they lack is a coherent system for turning intent into action.

And often, it’s not resistance to change - it’s awareness. As one executive said to me years ago:

“Either you know something I don’t know, or I know something you don’t know.”

That moment of realization matters. Because once you see the system, you can’t unsee it.

The Patchwork Organization

Instead of a coherent system, what typically exists is a patchwork:

• Strategy created at the top

• Priorities diluted through layers

• Decisions made inconsistently—or worse, not made

• Accountability assumed—but not structured

Individually, each of these seems manageable. Together, they create a system.

And that system produces exactly what you see:

Drift. Delay. “Execution challenges.”

Not because people aren’t trying - but because the system isn’t designed to produce anything else.

Why Proven Frameworks Still Fall Short

There’s no shortage of good thinking in this space.

Frameworks like Traction, Good to Great, and approaches like SAFe all get something fundamentally right:

Execution improves when the business operates as a system—not a collection of initiatives, functions, or departments.

They emphasize disciplines such as:

• Clear vision

• Right people in the right roles

• Measurable priorities

• Structured cadence

These are not theoretical - they are practical, proven, and necessary. And yet…

In more complex organizations, even when these elements exist, execution still stalls.

The Missing Layer: Cognitive and Structural Reality

The gap is this:

Execution at scale is not just operational - it is cognitive and structural.

This is where most frameworks stop short.

At smaller scale, structure and discipline are often enough. At enterprise scale, they are not.

Because what actually determines execution is not just:

• What is defined

• What is planned

But:

• How decisions are made

• Where authority truly sits

• How trade-offs are resolved

• How attention is allocated over time

Research from McKinsey & Company has consistently shown that the majority of strategic initiatives fail to deliver their intended outcomes - often due to breakdowns in alignment, decision-making, and coordination, not the strategy itself.

Similarly, Michael Porter has long argued that strategy only has meaning when it is translated into consistent choices and trade-offs across the organization.

That’s where most organizations struggle - not in defining strategy, but in sustaining coherent choices over time.

What Your System Is Really Doing

Every organization has a system - whether it’s designed or not.

And that system is perfectly calibrated to produce:

• The decisions it currently makes

• The priorities it currently tolerates

• The level of accountability it currently enforces

Not the ones it aspires to.

This is why leadership teams often feel the tension between:

• What they say matters

• What actually gets done

Because the system—not the intent—wins every time.

The Illusion of Progress

When execution breaks down, the default response is predictable:

• Introduce new initiatives

• Adopt new frameworks

• Change the language

• Re-double efforts or launch another transformation effort

On the surface, it looks like progress.

In reality, it’s often movement without change. (and often compound the root cause issues)

Because the underlying system remains untouched. And so the cycle repeats.

A More Useful Question

Instead of asking:

“How do we improve execution?”

A better question is:

“What is our system actually designed to produce?”

That question forces a different level of honesty. It shifts the focus from:

• Symptoms to structure

• Activity to outcomes

• Intent to design

And it opens the door to meaningful change.

Where to Look First

If you want to understand your system, don’t start with frameworks.

Start by examining:

1. Decision-Making

• Where are decisions really made?

• How consistently are they made?

• What happens when decisions are unclear?

2. Prioritization

• What actually gets resourced?

• How many “priorities” exist at once?

• What gets stopped—or never does?

3. Accountability

• Who is truly accountable for outcomes?

• Is accountability explicit—or assumed?

• What happens when commitments aren’t met?

4. Operating Rhythm

• How often do you revisit priorities?

• How do you inspect and adapt?

• Is there a cadence—or just activity?

These are not process questions. They are system design questions.

The Leadership Imperative

This is ultimately a leadership issue.

Not because leaders are failing - but because:

Most leadership teams have never been taught to think in systems.

They think in:

• Strategy

• Initiatives

• Functions

• ...and often $ and FTE headcount

(and truth be told, often in terms of cost control at the expense of value realization - that will be a hole post unto itself later!)

But execution lives in the connections between them.

That’s the work.

Final Thought

Execution doesn’t fail.

It delivers exactly what your system is built to produce.

So the question isn’t:

“How do we execute better?”

It’s:

“What have we actually designed our organization to do?”

In the next piece, I’ll explore a question most leadership teams believe they’ve already solved:

Are we actually aligned—or just agreeing in meetings?

If you’re honest—where does execution really break down for you:

Alignment, decision-making, or accountability?