The Soil Before the Seeds: Why Strategy Fails Long Before Execution Begins

The strategy was clear. The priorities were well defined. Progress was being tracked through dashboards filled with metrics, milestones and colourful status indicators. Green dominated the screen. From a distance, everything looked healthy.

And yet something felt off.

The conversation in the room wasn't about customers, outcomes or value. It was about updates, reporting, governance and status meetings. We debated whether templates had been completed, whether review forums had taken place, and whether another meeting was required to discuss the outcomes of the previous one. Everyone appeared busy, committed and productive.

Yet no one could confidently answer a much simpler question: Were we actually getting closer to the outcomes we set out to achieve?

That moment has stayed with me because, over the years, I have realised it wasn't unique. Variations of that same conversation take place in organisations every day. We spend enormous amounts of time thinking about strategy. We develop ambitious plans, launch transformation programmes, redesign operating models and invest in new technologies. We establish governance structures. Sometimes, if we're feeling particularly committed to the cause, we create governance structures responsible for overseeing the governance structures.

At that point, everyone becomes exceptionally busy. Whether anything is actually moving is often another matter entirely.

After six years leading Ways of Work transformation within a large banking environment, I have arrived at a conclusion that initially felt uncomfortable but has since become impossible to ignore:

Execution is the ultimate strategy.

Not because strategy lacks importance. Strategy matters enormously. It gives organisations direction. It defines ambition and creates alignment around what matters most. It tells us where we want to go and why it matters. But strategy only becomes meaningful when people translate it into daily decisions, behaviours and outcomes. Until then, it remains little more than intent.

The longer I work in transformation, the more convinced I become that most organisations do not fail because they lack strategy. There is rarely a shortage of intelligent people, thoughtful plans or bold ambitions. Instead, they fail because they underestimate the conditions required to turn those ambitions into reality.

The issue is rarely the quality of the seeds.

The issue is the quality of the soil.

That realisation emerged during our own transformation journey.

Like many organisations, we adopted Objectives and Key Results (OKRs) to strengthen the connection between strategy and execution. The promise was compelling. Greater focus. Clearer priorities. Stronger alignment. Better outcomes. Who wouldn't want that?

We invested heavily in capability development. We trained leaders and teams. We established communities of practice. We implemented supporting tools and secured executive sponsorship. From the outside, it looked like a textbook transformation programme.

The challenge was that organisations do not execute strategy through frameworks. They execute strategy through people.

While OKRs gained traction within leadership circles, they often struggled to achieve the same momentum where value was actually being created: inside teams. At first, our response was predictable. We assumed the answer lay within the framework itself. Perhaps we needed more communication. Perhaps more training. Perhaps stronger governance. Perhaps, naturally, another workshop.

I've attended enough transformation workshops over the years to suspect there's an entire economy powered almost entirely by sticky notes and flipcharts. Every workshop begins with optimism and energy. Every workshop ends with photographs of colourful walls and enthusiastic commitments.

The challenge is that sticky notes don't create outcomes. People do.

Eventually we realised we were focusing our attention in the wrong place. The question wasn't whether the framework was good enough. The question was whether the environment around it was healthy enough.

That distinction changed everything.

One lesson became impossible to ignore: you cannot install OKRs.

They're not software. They're not project milestones. They're not something that becomes successful simply because it has been deployed. Like every management practice, they depend entirely on the conditions in which they operate.

I watched teams create well-crafted objectives and thoughtful key results. Workshops were productive. Dashboards looked healthy. The artefacts were often excellent. Yet outcomes didn't always follow.

Over time, we discovered why.

People didn't always feel safe enough to tell the truth.

They weren't always comfortable saying, "I don't know." They hesitated to admit, "This isn't working." They worried about raising concerns, challenging assumptions or suggesting that the organisation might be solving the wrong problem altogether.

Those statements may sound ordinary, but they are often the most valuable words an organisation can hear. The moment people stop feeling safe to speak honestly, leaders lose access to reality. Decisions become disconnected from the truth. Optimism replaces evidence. Assumptions replace understanding.

The framework wasn't broken.

The environment beneath it was.

That insight forced me to rethink how I viewed transformation. Too often organisations ask frameworks to solve problems that only leadership can solve. We introduce methodologies when what we really need is trust. We build processes when what we really need is ownership. We launch programmes when what we really need is behaviour change.

Frameworks certainly matter. But culture matters more.

Without the right conditions, even the best strategic tools become organisational theatre. Meetings continue. Dashboards are updated. Reports are distributed. Scorecards remain reassuringly green. Meanwhile, the outcomes remain stubbornly unchanged.

One of the most humbling moments in our own journey came when we realised that, despite our good intentions, we had become experts in compliance.

Whenever adoption slowed, our response felt logical. We added governance. Then reporting. Then oversight. Then review forums.

Every decision seemed sensible at the time.

The conversation usually started with something like this: "If adoption isn't happening, perhaps we need better visibility."

A dashboard followed. Then a reporting template. Then additional controls. Then another layer of governance.

Before long, we had created an impressive machine designed to monitor adoption rather than improve outcomes.

I've seen this happen repeatedly. At one stage it genuinely felt as though we were holding meetings to discuss updates generated by meetings that existed to review outputs produced by earlier meetings. Everyone was busy. Everyone was accountable for something.

Yet genuine ownership remained surprisingly difficult to find.

Looking back, we threw almost everything at the problem except the one thing we actually needed: trust.

That isn't an easy thing for leaders to admit.

We were trying to help. We were trying to create consistency. We were trying to accelerate progress. Yet in doing so, we were unintentionally making ownership harder rather than easier.

That experience taught me one of the most important lessons of my career: Mandating compliance often kills commitment.

People rarely embrace change because they're told to.

They embrace change because they experience its value.

Around the same time, another capability began reshaping our thinking: Flow.

What attracted me wasn't the framework itself. It was the honesty it introduced into organisational conversations. For the first time, teams could see how work genuinely moved through their systems. They could identify bottlenecks, understand lead times and observe where value was becoming stuck. They could see, often for the first time, the gap between how they believed work flowed and how it actually flowed.

The conversation shifted from assumptions to evidence.

And once people can see reality clearly, something remarkable happens. The quality of decision-making improves.

Most executives eventually ask the same question: "When will it be done?"

The answers are often fascinating. Some are grounded in data. Some are based on experience. Some are based on optimism. And some appear to rely on little more than hope and a favourable alignment of planets.

We've all seen projects that begin with confident delivery dates. Those dates become targets. The targets become aspirations. The aspirations eventually become conversations about why the original targets were unrealistic.

Flow introduced something refreshingly different: reality.

Not pessimism.

Reality.

And reality turns out to be incredibly useful when trying to create value.

As predictability improved, trust began to grow. Stakeholders could make better decisions. Teams could have more meaningful conversations. Expectations became more realistic. Delivery became more predictable.

Perhaps most importantly, people stopped focusing on appearing busy and started focusing on being effective.

I've come to believe that predictability is one of the most underrated leadership capabilities in modern organisations. Trust grows when people consistently do what they said they would do.

And trust changes everything.

As our transformation matured, another insight emerged: organisational maturity follows a sequence.

People need visibility before they can improve. They need understanding before they can optimise. They need predictability before they can confidently commit to outcomes.

For years, I thought transformation was about introducing better practices. Now I believe it's primarily about helping people ask better questions.

Eventually, teams stopped asking, "How much work did we complete?" and started asking, "Did this create value?"

They stopped asking, "Did we deliver what was requested?" and started asking, "Did we solve the right problem?"

That shift sounds small. It isn't.

It's transformational.

Because the moment people become obsessed with outcomes rather than outputs, strategy stops being something discussed during executive planning cycles. It becomes something lived every day through thousands of decisions, conversations and trade-offs.

The longer I work in transformation, the more convinced I become that transformation is not fundamentally a delivery challenge.

It's a leadership challenge.

The irony is that many of the skills that make us successful leaders can become obstacles during transformation. We build careers on having answers. Transformation requires better questions. We build careers on reducing uncertainty. Transformation requires experimentation. We build careers on maintaining control. Transformation requires trust.

That's not a procedural shift.

It's a personal one.

And perhaps that's why it's so difficult.

As our transformation evolved, we began describing the connection between strategy and execution as the Golden Thread of Value. Strategy provides direction. Outcomes define success. Discovery identifies opportunities. Flow enables delivery. Measurement enables learning.

Together, they create line of sight between executive intent and customer impact.

When that connection exists, strategy stops being an annual event. It becomes visible in the everyday decisions people make. It becomes visible in prioritisation discussions, customer conversations, trade-off decisions and team commitments.

That is where execution becomes the ultimate strategy.

Too many organisations are still searching for the next methodology, operating model or three-letter acronym that will finally solve their execution challenges. There is always another framework promising better alignment, faster delivery or improved performance.

After years spent helping organisations navigate change, I have become convinced that most do not have a framework problem.

They have a conditions problem.

People do extraordinary things when they feel trusted. They offer their best thinking when they feel safe. They sustain change when they understand why their work matters. They challenge assumptions when they know their voices will be heard.

The organisations that succeed are rarely those with the most impressive methodologies. They are the ones where leaders create environments that allow people to thrive. They are the organisations where learning matters more than certainty, where ownership matters more than compliance and where honest conversations matter more than polished reports.

Which brings me back to that leadership meeting all those years ago.

I can still picture the dashboards. I can still remember the green indicators. I can still recall how confident everything looked on the surface.

But I also remember the feeling that something essential was missing.

What I understand now is that we had become fascinated by the seeds. We spent our time discussing strategy, frameworks, governance and performance measures. We focused on what we were planting.

We paid far less attention to where we were planting it.

And that is the question every leader should ask before launching another programme, approving another strategy deck, or introducing another framework designed to improve execution:

Have we created the conditions for success?

Because long before value reaches a customer, long before outcomes appear on a dashboard, and long before strategy becomes reality, something else determines whether success will ever take root.

The soil.

And every leader, whether they realise it or not, is a gardener.

The seeds matter. Ambition matters. Strategy matters.

But great gardeners know something that organisations too often forget: no seed, however brilliant, can flourish in poor soil.

The future of our organisations will not be determined by the plans we write.

It will be determined by the environments we create for people to bring those plans to life.