Why strategic plans fail: the real gap between strategy and daily practice

Most organisations have a strategic plan that looks great on paper. The direction is clear, the KPIs are listed, targets are documented, and someone's name sits next to every goal. There's even a reporting rhythm to keep it all on track.

On paper, it all makes sense.

But here's the real question: does any of it show up in what people actually do each day?

Because a strategic plan isn't judged by how coherent it looks in a document. It's judged by whether it becomes coherent in the daily practice of every employee, team and leader across the organisation.

The real test of a strategy isn't the document — it's the behaviour.

Once a strategic plan leaves the boardroom, it has one job left: shape what people actually focus on.

That means it has to influence what teams stop doing, what gets discussed in meetings, what gets measured, what gets resourced, and what people are learning to do better. If it doesn't touch those things, it's not really a strategy in action, it's just a document.

After years of working with organisations on exactly this problem, one pattern shows up again and again: there's a real gap between what leaders say they're focused on and what their teams are actually doing week to week.

An organisation can have a strong strategic plan and a well-thought-out annual improvement plan, but if team goals, divisional priorities, individual performance plans, and professional learning are all pulling in slightly different directions, the organisation doesn't move as one system. It moves as a collection of very busy, disconnected parts.

The ants' nest problem

Here's a simple way to picture it: think about what happens when you kick an ant's nest.

Instantly, there's movement everywhere. Every ant is active. Everyone is carrying something, reacting, going somewhere. From a distance, it looks like intense activity and effort.

But it isn't coordinated. It's chaos with energy behind it.

That's exactly what misaligned improvement work looks like inside a business. When team goals, divisional priorities, and individual plans aren't connected to the bigger organisational direction, people are working hard but that effort isn't compounding into real progress.

And to be clear, the problem is never that people aren't trying. Most people are working incredibly hard, juggling more than is reasonable, and they care about doing good work. The issue is that effort alone doesn't guarantee strategic progress. Effort has to be pointed somewhere specific for it to count.

Strategy isn't achieved by the plan itself.

A strategic plan doesn't execute itself. It's brought to life through hundreds of smaller decisions the routines, conversations, trade-offs, and learning moments that happen across an organisation every single week.

That only works when the annual improvement plan isn't treated as a compliance document sitting off to the side, "owned" by the executive team and rarely looked at again. It has to actively shape what teams prioritise, what leaders ask about in check-ins, what individuals are developing, and what professional learning is actually designed to build.

For that to happen, alignment needs to run in two directions: vertically and horizontally.

Vertical alignment: can people see the line from their work to the big picture?

Vertical alignment means there's a clear, visible line running from the strategic plan, down through the annual improvement plan, into team and divisional plans, and finally into individual goals and professional learning.

This isn't about vague statements like "We all contribute to the vision." It's about people being able to point to their own work and explain, specifically, how it connects to where the organisation is trying to go.

Horizontal alignment: are teams working with each other, not around each other?

Vertical alignment alone isn't enough. Teams and divisions also need to be aligned with each other.

Without this, one team ends up prioritising one thing, another team chases something completely different, and a third unknowingly duplicates work or pulls in the opposite direction,  not out of bad intent but simply because the connections between teams were never made visible.

What happens when alignment breaks down

When vertical and horizontal alignment are both weak, improvement work becomes fragmented. It's a familiar pattern: one team focuses on building capability, another is buried in compliance tasks, a third is chasing a local issue that may or may not connect to the annual plan, and individuals set personal goals based on whatever feels easiest to write down rather than what actually matters.

Professional learning suffers the most in this scenario. Instead of being a deliberate mechanism for building the capability the strategy actually needs, it turns into a menu of interesting-sounding courses and workshops engaging, maybe but disconnected from the bigger goal. And all of that still costs time, money, and energy.

The questions good improvement architecture should help you answer

Strong improvement architecture doesn't just organise information it helps leaders make better decisions about where attention and resources should go. It should let leaders genuinely ask:

  • Does this team goal actually contribute to our annual improvement priorities?

  • Does this professional learning build the capability we need most right now?

  • Do individual goals reflect the direction we're actually trying to move in?

  • Are we collecting this data because it helps us understand progress or just because it's available?

Alignment doesn't mean sameness

It's worth being clear about what alignment isn't. It's not about control for the sake of control. It's not about forcing every team to write identical goals, stripping out local context or squeezing individuals into a narrow, one-size-fits-all version of development.

Done well, alignment does the opposite of all that. It helps teams and individuals understand exactly how their specific work contributes to something bigger, while still leaving room for the nuance of their role, their context, their strengths, and their own development needs.

The goal was never sameness. The goal is alignment.

Why this clarity actually matters

When improvement plans are properly aligned, people can trace a clear thread from their day-to-day work all the way through to the broader vision. They understand why a priority matters, how it connects to the bigger direction, what their team is doing about it, what they personally need to strengthen, and how progress will actually be tracked over time.

That clarity pays off in real, practical ways:

  • It reduces duplicated effort across teams.

  • It protects people from chasing every new idea that shows up.

  • It helps leaders make smarter trade-offs when time and energy are limited.

  • It makes professional learning a genuinely meaningful investment in the capability the plan needs, not just a box-ticking event.

The cost of disconnection

Picture the alternative: the strategic plan says one thing, the annual improvement plan tracks something else, team plans focus elsewhere again, and individual goals are disconnected from all of it.

Reporting becomes messy almost immediately. You might still be collecting solid data on what's happening, but that data won't tell a coherent story about whether the organisation is actually improving in the areas it said mattered most.

This is exactly why operationalising strategy is about more than picking a few KPIs or building a slick dashboard. It's about building the connective tissue between intention, action, learning and evidence making sure big goals don't stay big and abstract but get translated into practical, everyday work at every level of the organisation.

The question worth asking instead

So maybe the most useful question isn't "What does our strategic plan say?"

A better question is: "Can our people see themselves in this work?"

Can teams see how their improvement focus connects to the plan? Can individuals see how their goals and professional learning support it? Can leaders honestly tell whether effort across the organisation is aligned or whether people are scattering in different directions with good intentions and exhausted calendars?

What this means for your organisation

When plans are genuinely aligned, improvement work stops being a collection of disconnected tasks and becomes a shared direction. And in organisations where time, attention, and energy are already stretched thin, that shared direction isn't a nice-to-have.

It's the difference between everyone working together toward the same goal and everyone scattering, running hard, but going nowhere together.

FAQ

1. What is strategic alignment in an organisation?

It's when a strategic plan actually shows up in the daily decisions individuals and teams are making, rather than remaining as an abstract idea. Alignment is when your team can see how their work connects to it. 

2. Why do strategic plans fail to translate into daily practice?

Usually not from a lack of effort, but a lack of clarity.. People look at what’s urgent, what their boss is chasing them for. Without a clear thread linking the plan to their actual work, this urgency is what shapes their priorities - not the plan.

3. What's the difference between vertical and horizontal alignment?

Vertical is the line from strategic plan → annual plan → team plans → individual goals. Horizontal is how well teams stay coordinated with each other, so they're not duplicating or working against one another.

4. How can leaders tell if their teams are actually aligned with the strategy?

Ask if people can explain, specifically, how their work supports the priorities not just "We all contribute to the vision."

5. Does alignment mean every team has to work on the same goals?

No. It means each team's work ladders up to the shared direction while still leaving room for local context and different strengths.


Previous
Previous

Data doesn't belong in a silo — it belongs in every decision

Next
Next

Why data doesn't create learning. Curiosity does