Your Strategy Didn't Fail. Your Execution Never Had a Chance.

Why capable teams struggle to deliver strategic priorities, and six questions every executive should answer before blaming execution.

The strategy session went well.

The senior leadership team spent two days discussing the organization’s future. The opportunities were compelling, the objectives ambitious but achievable, and everyone seemed to understand where the organization needed to go.

The strategy was communicated. Leaders explained the priorities, outlined the objectives, and encouraged their teams to get behind the plan.

Then Monday arrived.

Managers returned to their existing responsibilities. Departments continued working toward objectives that hadn’t changed. Budgets remained largely untouched, employees were already busy, and those assigned to lead new initiatives discovered they needed to negotiate for resources and decisions they didn’t have the authority to make.

The strategy was new. The organization responsible for delivering it hadn’t fundamentally changed.

Six months later, the executive team reviewed progress. Projects were behind schedule, decisions were taking too long, and teams were struggling to balance the new initiatives with everything they were already expected to deliver.

Naturally, the conversation turned toward execution.

Why weren’t people delivering? Where was the accountability? Why weren’t managers making the necessary progress?

But what if the execution failure had started long before anyone was asked to execute anything?

A strategic decision is not an organizational commitment until leadership has established the conditions necessary to execute it.

That’s a distinction far too many leadership teams overlook.

Strategy Is a Choice. Execution Is a Commitment.

Strategy establishes direction. It identifies where an organization intends to focus, what it wants to accomplish, and which opportunities leadership believes are worth pursuing.

Execution demands something more. It requires leaders to determine what the organization will actually do differently to turn those intentions into results.

Who owns the outcome? What resources are available? Which decisions can be made without additional approval? What existing work will take a lower priority? How will competing demands be resolved?

These aren’t administrative details to sort out after the strategy has been announced. They’re part of the strategic decision itself.

I’ve experienced what happens when those decisions aren’t properly aligned.

During my time at 1st Canadian Division Headquarters, we received direction from higher headquarters to focus on a particular region of the world and a defined set of missions.

Our Division Commander, however, consciously chose to take the organization in a different direction.

The result was confusion across the headquarters. Different parts of the organization were being pulled toward different priorities, and what one group understood to be important wasn’t necessarily consistent with what another was working toward.

People were trying to accomplish their responsibilities, but we weren’t necessarily working toward the same destination.

As a leader within that headquarters, I couldn’t resolve the strategic disconnect at the top. What I could do was try to protect my team from its consequences.

I focused on keeping their priorities as clear and consistent as possible, filtering out unnecessary distractions, and shielding them from the competing demands affecting the wider organization. My goal was to give them enough stability and direction to do their jobs effectively, even when the larger organization wasn’t providing that clarity.

It wasn’t about ignoring direction or choosing which senior leader I preferred to follow. It was about doing what I could, within my responsibilities, to minimize the confusion landing on my people.

That experience reinforced something I’ve carried throughout my leadership career.

When senior leaders fail to align their strategic direction, the burden of managing that confusion falls on the people below them.

And those people often have the least authority to resolve it.

The organization doesn’t necessarily grind to a halt. Meetings continue, reports get written, and teams remain busy. But effort becomes fragmented, decisions become harder, and people spend valuable time reconciling priorities that should have been resolved above them.

From the executive level, that can look like an execution problem.

From inside the organization, it feels very different.

The Execution Gap Often Begins at the Executive Table

When an important initiative stalls, it’s natural to examine the people responsible for delivering it.

Did the project lead manage the timeline? Did the department meet its commitments? Did the team demonstrate sufficient urgency?

Those are legitimate questions. Accountability matters, and capable people can certainly fall short of reasonable expectations.

But before assigning responsibility for an execution failure, senior leaders need to examine the conditions they created.

Consider a manager who receives responsibility for a major initiative while continuing to carry a full portfolio of existing commitments. The new project is described as a top priority, but none of the manager’s previous objectives have changed.

Another department controls resources the project needs. Its leader has different performance measures and equally legitimate commitments. Neither manager has the authority to resolve the conflict.

Both are working hard. Both believe they’re doing what leadership expects.

Yet the initiative isn’t moving.

Senior leaders may have agreed on the importance of the initiative without agreeing on what that decision requires from the organization.

The ambiguity doesn’t remain in the boardroom. It travels downward, where managers and employees are left to reconcile it through their daily decisions.

Some protect existing commitments. Others shift resources toward the new initiative. Some attempt to do everything, spreading their attention across more work than they can reasonably deliver.

From above, those decisions may appear inconsistent or poorly coordinated. From the perspective of the people making them, they may be the only practical options available.

Accountability for execution must extend beyond the people doing the work to the leaders who establish the conditions in which that work happens.

Announcing a Priority Doesn’t Create Capacity

One of the most common mistakes leaders make is assuming that declaring something important somehow creates the capacity to deliver it.

It doesn’t.

Every major initiative consumes organizational resources. Not simply money, but people’s time, attention, expertise, and decision-making capacity.

Launching a new product, entering a new market, implementing a technology platform, or restructuring an operation all require effort that must come from somewhere.

If employees are already fully committed, adding another initiative doesn’t magically expand their capacity.

Something gives.

Deadlines slip, quality suffers, operational responsibilities receive less attention, or employees begin working longer hours to compensate. Managers make informal decisions about which commitments will receive less effort because nobody above them has made those decisions explicitly.

The problem isn’t necessarily that the new initiative lacks merit. It’s that leadership has approved more work than the organization can reasonably carry.

A credible strategic commitment requires more than identifying what needs to happen. It requires acknowledging what the organization can realistically support.

And that means asking an uncomfortable question:

What are we prepared to stop doing so that this new priority has a realistic chance of succeeding?

If the answer is nothing, leadership needs to reconsider the initiative’s timing, scope, or resources.

Otherwise, the organization may be committing to an outcome it was never positioned to achieve.

Accountability Without Authority Creates a Trap

Imagine assigning a director responsibility for launching a new service.

The director owns the deadline, coordinates the project, and reports progress to the executive team. But engineering resources belong to another department, operational changes require separate approvals, and routine spending decisions must return to senior leadership.

The director is accountable for the outcome but doesn’t control many of the decisions necessary to deliver it.

Every delay becomes their problem, even when resolving it requires authority they don’t possess.

Assigning accountability is relatively easy. Giving someone the practical ability to influence an outcome requires considerably more thought.

That doesn’t mean every initiative leader needs unlimited authority. Senior executives must retain responsibility for significant financial commitments, organizational risk, and decisions that affect the broader business.

But the boundaries need to be understood.

What can the initiative leader decide independently? What requires approval? Who resolves disagreements between departments? How quickly can an obstacle be escalated and addressed?

Without those answers, leaders can create an environment where people are responsible for results they have limited ability to influence.

If you’re holding someone accountable for an outcome, you need to give them sufficient authority to influence it.

Otherwise, you’ve transferred the pressure without transferring the means to act.

Alignment Isn’t Agreement

An executive team can agree that an initiative is important while holding fundamentally different views about what should take precedence when priorities collide.

Sales may be focused on growth. Finance may be trying to control spending. Operations may be protecting delivery reliability, while product development is pushing innovation.

Each objective can be perfectly reasonable. The problem emerges when those objectives compete for the same people, resources, and decisions.

Should engineering prioritize an existing customer commitment or the new product? Should the organization invest in capacity ahead of demand or wait until the market proves the opportunity? Should a launch proceed with known limitations or be delayed to protect the customer experience?

These aren’t simply operational disagreements. They’re strategic trade-offs.

And if senior leaders haven’t established which outcomes take precedence, departments will make those decisions independently.

This is what makes strategic alignment more demanding than getting everyone to agree with a presentation.

Leaders need to understand not only where the organization is going, but what that direction means when competing demands arise. Sometimes that requires difficult conversations about resources, existing commitments, and which objectives must temporarily take a back seat.

Healthy organizations need debate, and strategic decisions frequently involve competing interests. But once a direction is established, the leadership team has a responsibility to reconcile those priorities rather than leaving the contradictions for employees to manage.

Alignment isn’t everyone agreeing that a strategy sounds good. It’s leaders making consistent decisions about what matters when priorities compete.

Without that consistency, an organization can be busy, committed, and capable while still struggling to make meaningful progress.

Execution Reviews Should Produce Decisions, Not Just Updates

Even when an organization begins with clear priorities, sufficient resources, and appropriate authority, execution still requires active leadership.

Circumstances change. Assumptions get tested. Obstacles appear that weren’t visible during planning.

Organizations need a practical rhythm for examining progress, identifying constraints, and responding while there’s still time to make a difference.

Unfortunately, many execution reviews become reporting exercises.

Teams prepare updates, explain milestones, and assign colours to their project status. Executives review the information, ask questions, and schedule the next meeting.

Everyone leaves knowing more about the project’s status, but the obstacles preventing progress remain unresolved.

A useful execution review should accomplish something more.

It should expose constraints, clarify competing priorities, authorize decisions, and adjust resources or expectations when necessary.

Leaders also need to distinguish activity from progress. A team can hold meetings, produce documents, and complete dozens of tasks without moving materially closer to the intended outcome.

Conversely, a missed milestone may reveal a flawed assumption that needs executive attention rather than a performance reprimand.

The purpose of reviewing execution isn’t simply to determine whether people are following the plan. It’s to ensure the organization continues creating the conditions necessary to achieve the intended result.

A useful execution review produces decisions, not merely updates.

The Execution Readiness Test

Before announcing or launching a major initiative, I believe senior leaders should be able to answer six questions.

These aren’t intended to create another elaborate planning exercise. They’re a practical way to determine whether the organization is prepared to deliver what leadership has decided.

1. Outcome: What result are we trying to achieve?

Objectives such as growing the business, improving customer experience, or modernizing operations may describe worthwhile ambitions, but they don’t necessarily define a result.

What specifically will be different if the initiative succeeds? How will we recognize progress? What evidence will tell us whether the intended outcome has been achieved?

People need a shared understanding of the destination before they can make effective decisions about how to get there.

2. Ownership: Who is genuinely accountable for delivering it?

Every significant initiative needs someone responsible for driving the outcome, coordinating the necessary effort, and bringing unresolved problems to the appropriate decision-makers.

A committee can support the work, but collective participation shouldn’t obscure individual accountability.

Ownership also needs to be realistic. Assigning another major initiative to someone already managing several competing priorities doesn’t necessarily create genuine ownership.

3. Authority: Can that leader influence the result?

Accountability must be matched with appropriate decision-making authority.

Which decisions can the leader make? What resources can they access? Where are the boundaries? How are disagreements or obstacles escalated?

The goal isn’t to remove executive oversight. It’s to prevent routine decisions from becoming recurring bottlenecks while holding the initiative leader responsible for the resulting delays.

4. Capacity: What have we actually committed?

A budget allocation doesn’t automatically mean the necessary capacity exists.

Which people will do the work? How much time can they realistically contribute? What expertise is required? What operational commitments must continue?

If success depends on employees absorbing additional work indefinitely, that assumption deserves scrutiny before the initiative begins.

5. Alignment and trade-offs: What takes precedence when priorities compete?

Does the executive team genuinely share an understanding of what matters most? Are different departments working toward compatible outcomes? Have existing commitments been adjusted to reflect the new direction?

And perhaps most importantly, what will stop, slow down, or receive fewer resources to make the initiative possible?

Not every existing responsibility can be reduced. Customer commitments, safety requirements, legal obligations, and essential operations may leave little room for adjustment.

But that reality must influence the strategic decision.

If leadership cannot reconcile competing priorities, it shouldn’t expect employees further down the organization to resolve those conflicts on its behalf.

6. Execution rhythm: How will we respond when reality changes?

Establish a review process that provides meaningful information early enough to act.

Which milestones matter? What indicators demonstrate progress? What problems require escalation? Who has authority to adjust resources, priorities, or the approach itself?

Most importantly, how will the organization move from identifying a problem to making a decision?

A reporting process that repeatedly documents the same unresolved obstacle isn’t an effective execution system.

These six questions won’t eliminate uncertainty or guarantee success. They will, however, reveal whether leadership has made a credible organizational commitment or simply announced an ambition.

Not Every Failure Is an Execution Failure

Not every unsuccessful initiative is evidence of poor executive leadership.

Sometimes the strategy itself is flawed. Sometimes external conditions change in ways nobody could reasonably anticipate. And sometimes individuals fail to meet legitimate expectations despite having the resources, authority, and support necessary to succeed.

Those situations require different responses.

A flawed strategy needs reconsideration. Unexpected conditions require adaptation. Poor individual performance may require coaching, clearer expectations, or accountability.

But an initiative that was never properly resourced, aligned, or empowered requires leadership to examine its own decisions.

That’s where the conversation often becomes uncomfortable.

It’s easier to ask why a project manager missed a deadline than to examine whether the executive team created competing priorities.

It’s easier to demand greater accountability than to acknowledge that the person responsible lacked the authority to make necessary decisions.

And it’s easier to announce another strategic initiative than to confront the fact that the organization is already struggling to deliver its existing commitments.

Senior leaders need to resist the temptation to diagnose every disappointing outcome as a failure by the people below them.

They need to examine the entire chain of decisions that shaped the organization’s ability to deliver.

What did we expect? What resources did we provide? What authority did we grant? Which priorities were competing? What did we leave unresolved?

And what role did our own leadership decisions play in the outcome?

This isn’t about removing accountability from managers and employees. It’s about ensuring accountability reaches the people whose decisions created the operating environment in the first place.

Before You Launch Another Initiative, Examine the One You Already Have

Think about one major initiative currently underway in your organization.

Not the easiest project or the one receiving the most attention. Choose something important that isn’t progressing as well as leadership expected.

Now examine it through the six questions in the Execution Readiness Test.

Can everyone involved describe the intended outcome? Is ownership clear? Does the accountable leader have the authority to influence the result? Have the necessary resources genuinely been committed?

Are departments working toward compatible priorities, and has leadership made the necessary trade-offs?

When obstacles arise, are execution reviews producing decisions or simply documenting the problems?

You don’t necessarily need another strategy session, a new project management framework, or an organizational restructuring.

Sometimes the most useful action is to resolve one decision that has been sitting unanswered, clarify one competing priority, or give a capable leader the authority needed to move forward.

Those changes may seem modest compared with the ambition of the original strategy.

But they’re often what makes execution possible.

And if you find yourself repeatedly asking why capable people aren’t delivering important initiatives, consider whether you’re examining the right problem.

Before questioning whether your people can execute the strategy, ask whether you’ve made execution possible.

Your organization doesn’t execute what leadership announces. It executes what leadership makes possible.

That’s a responsibility senior leaders cannot delegate.

If you’re a founder, business owner, or executive frustrated that capable people aren’t moving important initiatives forward, a Leadership Clarity Call can help you examine whether your leadership practices and organizational conditions are supporting execution or getting in its way.

Because sometimes your strategy didn’t fail.

Your execution never had a chance.