There’s a common narrative inside organizations when large initiatives break down.
Execution failed. The rollout wasn’t managed well. The teams didn’t deliver.
It’s a convenient explanation. And in many cases, it’s wrong.
Because by the time execution starts, the outcome is often already set.
For leaders responsible for large-scale rollouts, transformations, and multi-site deployments, this is a hard truth to sit with.
The real failure point is not always in execution. It is in the moment the initiative is approved.
The Hidden Cost of Getting Commitment Wrong
When a flawed initiative moves forward, it doesn’t fail immediately.
It moves. It consumes time. It consumes resources. It builds momentum.
And then it begins to struggle.
What looks like execution failure starts to appear:
- Missed timelines
- Budget pressure
- Coordination issues
- Increased oversight and reporting
But those are symptoms.
The real issue is that the system was never aligned to succeed.
Priorities were not clearly defined. Trade-offs were not enforced. Risks were acknowledged but not resolved.
So the pressure doesn’t disappear. It gets pushed downstream.
Into execution.
At that point, teams are not executing a clean plan. They are compensating for a flawed one.
And the emotional toll shows up quickly.
Leaders feel trapped by commitments already made. Teams feel the weight of expectations that don’t match reality. Confidence erodes, even when effort increases.
What This Article Gets Right
A recent article from LSE Business Review , “Why strategic initiatives fail before execution even begins” by Wilbert van den Berg , challenges the assumption that execution is where failure originates.
The author introduces a critical distinction.
What we often call an execution gap is actually a commitment gap.
In many cases, initiatives are set up under:
- Optimism bias
- Social pressure to move forward
- Incomplete understanding of constraints
By the time execution begins, key decisions have already narrowed the available paths.
The article draws a powerful parallel to industries like aviation and healthcare, where structured pre-commitment checks are used to surface risk before action is taken.
That insight is important.
But it only tells part of the story.
Where This Becomes Real in Practice
In real-world execution environments, especially across distributed operations, the impact of poor commitment shows up in very specific ways.
What was assumed to be aligned begins to fracture:
- Requirements are interpreted differently across teams
- Dependencies are discovered too late
- Sites encounter conditions that were never accounted for
- Vendors execute against incomplete or conflicting expectations
Execution doesn’t just struggle. It becomes reactive.
Organizations respond by adding:
- More governance
- More reporting
- More oversight
But none of those fix the underlying issue.
They increase friction.
And over time, the system becomes overloaded.
What looks like execution failure is actually structural stress that was introduced at the start.
A Different Way to Think About Readiness
Most organizations treat commitment as a milestone.
Something to reach. Something to celebrate.
But commitment should be treated as a filter.
A point where initiatives are tested against reality, not just ambition.
True readiness requires more than a strong business case.
It requires:
- Clear prioritization, where saying yes forces something else to stop
- Explicit trade-offs, not assumed alignment
- Honest assessment of constraints across teams, systems, and environments
- Defined conditions for success and failure before execution begins
And most importantly, it requires leaders to separate confidence from readiness.
Confidence pushes initiatives forward. Readiness determines whether they survive.
What This Means Moving Forward
If execution is where pressure shows up, commitment is where pressure is created.
And that shifts the responsibility upstream.
Before the next initiative moves forward, ask:
Have we actually cleared space for this to succeed or are we layering it on top of existing commitments?
Have we aligned on trade-offs or are we assuming teams will figure it out later?
Have we validated readiness across environments or just agreed on the plan?
Because once execution begins, options narrow quickly.
And what could have been corrected early becomes much harder to fix.
A Final Thought
The easiest time to prevent failure is before the work begins.
But that requires discipline most organizations don’t naturally apply.
Before approving the next initiative, take a step back and ask:
Are we committing to this because we believe in it or because we’ve proven it can actually work under real conditions?
That answer determines whether execution will move forward or slowly start to break.
"What Actually Matters" LinkedIn Newsletter