How to lead the development and implementation of corporate strategy aligned to organisational goals

Most businesses have a strategy. Far fewer have one that actually works.

The gap between a strategy that looks good in a boardroom presentation and one that drives real results is wide — and predictable. The same mistakes show up again and again, at every business size, in every industry. Understanding where strategy breaks down, and what it looks like when it holds together, is the starting point for doing it better.

What good strategy actually is

Before getting into what goes wrong, it helps to consider what strategy is supposed to be.

Richard Rumelt, one of the most respected thinkers on the topic, describes the kernel of good strategy as three things: a diagnosis of a problem or challenge, a guiding policy on how to approach it, and a series of coherent actions that bring that approach to life. Business leader and strategist Dr Julius Kipng’etich puts it more simply — strategy is "a deliberate effort to arrive somewhere."

My definition: "Strategy is what guides a business in answering one essential question: how are we going to remain sustainable — financially and otherwise — over time?"

That second part, the "otherwise," matters more than most leaders realise. Non-financial factors — how a business treats its employees, its relationship with the community, its reputation, its environmental impact, how it is perceived by stakeholders beyond shareholders — all have a direct bearing on financial sustainability. Sometimes the link is obvious. Often it is subtle. But ignoring it is not neutral; it opens the business to risk that could have been anticipated and planned for. A thorough strategy process uses systems thinking to trace how non-financial factors connect to financial outcomes, so that resource allocation decisions are grounded in reality rather than optimism.

Where strategy goes wrong in development

Strategy development tends to fail in two broad ways: by following the wrong template, and by staying too close to home.

The template problem

Many businesses build their strategy around the standard "vision, mission, key strategic objectives" framework because it feels like the right thing to do. It looks professional. It fills slides. But a framework is not a strategy. A list of aspirational statements with no clear line to operational reality is, at best, a to-do list with ambition attached.

The related trap is focusing so heavily on aspiration that the strategy loses touch with reality. This shows up as strategies that are impressive on paper but never quite get measured at the right level — while other problems quietly grow from neglect. On the opposite end, a strategy that is afraid of change tends to repeat previous years with more aggressive targets, which is not strategy either.

A third version of this problem is setting strategy that covers too many areas, or that is dressed in enough jargon that the people who need to implement it cannot translate it into action.

The perspective problem

Good strategy requires looking both far ahead and wide around the business — far enough to catch threats and opportunities that are coming but not yet obvious, and wide enough to pick up what is happening right now in the surrounding environment.

The risk of looking too far out and getting too excited is a strategy that tries to leapfrog progress while neglecting what is already in motion. The risk of looking too close is a strategy that gets caught off guard.

There is also a common tendency to look at competitors and industry leaders and try to replicate their approach. This usually leads to a strategy that fits someone else's context and ignores the unique circumstances of the business trying to adopt it.

Finally, strategy developed without input from employees and customers misses some of the most important and available information. Those closest to the work and the customer often carry insight that does not make it into boardroom conversations — but directly determines whether a strategy will hold up in practice.

Where strategy goes wrong in implementation

A strategy that cannot be implemented is not a strategy. It is a document.

The most common implementation failures trace back to communication and capacity.

Communication failures

Even a sound strategy will fail if the people responsible for bringing it to life do not understand it. This is not a matter of intelligence — it is a matter of translation. A strategy packaged as a polished slide deck that requires abstract reasoning to bridge the gaps between high-level intention and daily action puts the burden of interpretation on the wrong people.

There is also a critical difference between someone acknowledging a strategic goal and actually understanding and accepting what it means for how they work. Mistaking one for the other is a silent implementation killer.

Capacity failures

Ignoring how much is already in motion is one of the most consistent oversights in strategy development — and it plays out fully during implementation. Every person charged with delivering on a new strategic direction is already doing something. Strategy that does not account for existing workload, and does not actively create space — either through additional resources or by reducing existing activities — is setting people up to fail before they start.

Change management tends to be underestimated even when leaders know it will be needed. The degree of change that flows from a meaningful strategy shift usually requires more deliberate effort than is planned for.

Metrics are another area where implementation comes apart. Measurements need to be agreed on before implementation begins — not retrofitted after the fact. Vanity metrics, which look good but do not reflect real impact, have a way of filling the gap when true measurements have not been defined.

Building strategy that holds together

A few things make the difference between strategy that works and strategy that sits in a folder.

Start from the bottom up, not just the top down

Involving people at operational level during the development phase — not just in a consultation checkbox, but in a way that genuinely shapes the strategy — reveals whether a strategic objective is concrete enough to act on. If someone at the front line cannot explain what they would do differently to align with the strategy, the strategy is probably not clear enough yet.

Set metrics before you need them

Define what you will measure, and how, before implementation begins. Focus on measurements that reflect real impact — operational changes, customer outcomes, financial shifts — rather than measures that look good in a report but say little about whether the strategy is working.

Review it regularly

The era of the five-year strategy has passed. The variables that affect any business have become volatile enough that an annual and even quarterly review is now more useful. This does not mean the strategy itself has to change — a review that confirms nothing needs to change is a valid and useful outcome. But waiting years between reviews, or treating the review as a tick-box exercise, means the business is navigating with outdated information.

Check your strat

If the strategy cannot be summarised in one sentence — and that sentence cannot be used as a filter to say yes or no to opportunities — it is probably not clear enough yet.

That is not a criticism. It is a diagnostic. Most strategy documents, if they are honest, are closer to a broad ambition than a clear direction. The one-sentence test is a quick way to find out where the real work still needs to happen.

Good strategy is hard to build and harder to sustain. But it does not have to be complicated. It has to be honest, grounded, and clear enough that the people who need to live it can actually do so.