From Noise to Clarity | Track 9

STRATEGY EXECUTION: Why Good Strategy Dies in Execution #25

Visual Thinking for Transformation | Post 25 of 30

Before you read: take the strategy your organisation is currently executing and look at where the budget and the senior leadership time actually went last quarter. How closely does that match what the strategy says matters most?

Strategy has a problem that is rarely named as directly as it deserves. The problem is not that organisations produce bad strategies. Many organisations produce strategies that are genuinely insightful, clearly articulated, and well-evidenced. Strategy consultants are good at their work. Leadership teams are thoughtful about the choices they face. The quality of strategy documents has improved considerably over the decades during which this problem has persisted. The problem is that producing a good strategy and executing it are two different activities that require different things from an organisation, and most organisations are significantly better at the first than the second, without fully understanding why.

The gap between strategy and execution is one of the most consistently documented failures in business, studied, written about, and worried over in leadership circles for decades. But the explanations offered for it tend to focus on the execution side: the implementation was too slow, the change management was inadequate, the middle management did not cascade the strategy effectively, the organisation did not have the capabilities required. These explanations are not wrong. They describe real problems that real transformations encounter. But they tend to miss the deeper structural cause, which is that most organisations, in the moment of executing a strategy, continue to allocate their resources in the patterns that were established before the strategy was set. The new strategy has to fight for traction against an existing allocation pattern that was never updated to support it.

This is why good strategy dies in execution. Not because execution is hard, though it is. Not because the strategy was wrong, though sometimes it was. But because the strategy changed what the organisation said it was doing without changing where the organisation put its money, its best people, and its senior leadership attention. And in any organisation, what actually happens is determined far more by where the resources go than by what the documents say.

“Tell me where the money goes and I will tell you what the strategy actually is. The documents tell you what it says it is.”

The resource allocation gap

The most direct diagnostic question for why a strategy is not being executed is: does the resource allocation of the organisation, in terms of budget, headcount, and leadership time, reflect the priorities of the strategy, or the priorities of the organisation before the strategy was set? In almost every case where strategy execution is failing, the answer to this question is clear: the resource allocation has not materially changed. The strategy has been approved. The budget cycle that followed did not translate that approval into significantly different funding decisions, because the budget cycle used the same baseline, the same criteria, and the same political dynamics that had always governed it. The strategy set a new direction. The budget cycle continued in the old one.

This gap is structural and predictable, but it is almost never named in the strategy documents themselves. Strategies typically describe what will be different without specifying what will stop being funded to make room for the new priorities. That omission is not an oversight. It reflects a real difficulty: explicitly defunding something means taking it away from someone, which produces resistance that the strategy approval process was not designed to handle and that most leadership teams would prefer to avoid at the moment of the strategy launch, when energy and goodwill are at their highest. So the strategy is approved as an addition to what the organisation is already doing, and the resources to execute it are expected to come from somewhere that is never quite specified, which in practice means they come from nowhere.

In one case, a professional services firm approved a strategy centred on moving from high-volume, low-margin work toward lower-volume, higher-value advisory work. The strategy was well-reasoned and the market opportunity was real. Eighteen months after approval, the firm’s revenue mix had changed very little. The partners who drove the high-volume work were still the most celebrated in the firm’s culture, their billings were still the primary metric in the annual review, and the investment in the capabilities required for high-value advisory work was still marginal relative to the investment in the infrastructure that supported the high-volume model. The strategy had changed what the firm said it was doing. It had not changed what the firm rewarded, funded, or made it easiest to do. The resource allocation, which is the real strategy, remained unchanged.

“The real strategy is not the document. It is the pattern of where resources actually go, week after week.”

Why the budget cycle is the execution moment

If resource allocation is the mechanism through which strategy either lives or dies, then the budget cycle is the single most important execution moment in any strategy. It is the point at which the abstract priorities of the strategy have to be translated into specific numbers: this programme gets more, that one gets less, these roles are added, those are redeployed. It is also the moment at which the real tensions between the strategy and the existing organisation are most visible, and most consistently resolved in favour of the existing organisation because the existing organisation has advantages that strategic priorities do not.

The reasons for this are structural. Budget cycles are built around defending existing allocations, not building new ones. The people who come to the table with established programmes and established funding have the advantage of inertia, relationships, demonstrated track records, and the ability to point to concrete consequences of defunding their work. The new strategic priorities arrive without any of these. They are proposals rather than programmes, possibilities rather than proven contributors. In the political economy of a budget negotiation, this asymmetry consistently favours the established over the new, and the result is that each budget cycle marginally updates an existing allocation rather than genuinely reshaping it around the new strategy. The strategy is not ignored. It is consistently outweighed at the moment that actually determines what gets funded.

In one case, a technology organisation was attempting to shift significant investment from its legacy product maintenance, which consumed the majority of its engineering budget, toward new product development aligned with a strategic pivot to a different market. The strategy was clear and the logic was sound. But in three successive budget cycles after the strategy was approved, the engineering budget allocation changed by less than five percentage points in the direction the strategy required. The legacy product teams arrived at each budget cycle with detailed maintenance cost projections and clear evidence of the consequences of underfunding their work. The new product teams arrived with market opportunity analyses and early-stage prototypes that could not yet demonstrate the same kind of concrete consequence if underfunded. The budget allocators, under pressure to manage risk and maintain current customer commitments, consistently found the legacy teams’ arguments more immediately compelling. The strategy was not being ignored. It was being consistently outweighed at the moment that mattered most.

The fix required making the budget cycle itself an explicit strategy execution mechanism rather than a separate operational process. The CEO mandated that every budget discussion begin with a read of the strategy priorities and an explicit accounting of whether the proposed allocation moved toward or away from them. This did not resolve all the tensions, but it changed the default, from the existing allocation being the natural starting point to the strategy being the benchmark against which every proposed allocation was justified. The shift in engineering investment toward new products accelerated significantly in the following cycle.

“If the budget cycle is not explicitly designed to execute the strategy, it will execute the history instead.”

Making the strategy-resource link visible

The most practical intervention available to a leader who recognises the resource allocation gap is to make the link between strategy and resource visible in both directions: showing clearly where the strategy requires resources that are not currently allocated, and showing clearly where existing resource allocation is funding things that the strategy has deprioritised. Both of these are uncomfortable conversations in most organisations. Both are necessary if the strategy is to have any realistic chance of execution. Making them visible does not guarantee they will be resolved, but it makes it considerably harder to pretend they do not exist.

Showing where strategy requires unfunded resources forces the organisation to make explicit what was implicit in the approval: that executing this strategy requires stopping or reducing something else. This conversation is usually avoided at the strategy stage and deferred to the execution stage, where it becomes a source of frustration rather than a deliberate choice. Having it early, as part of the strategy approval rather than as a surprise during implementation, is considerably less comfortable but considerably more useful, because it is still possible at that point for the leadership team to make genuine decisions rather than managing the consequences of decisions that were never made.

Showing where existing resources are funding deprioritised activities is the more politically sensitive of the two conversations, because it directly challenges specific people’s budgets and programmes. But it is also the conversation that most directly creates the room for the new priorities to be funded. Without it, every new strategic initiative competes for resources against a baseline that was never examined, and the baseline consistently wins because it has history, relationships, and inertia on its side.

The most telling question to ask of any strategy at the moment of approval is not whether it is the right direction. It usually is. The question is whether the people approving it are also prepared to make the resourcing decisions that would give it a genuine chance of being executed, which means deciding what they will stop funding rather than simply deciding what they will add. Until that question is answered honestly, the strategy remains a document rather than a direction, and the execution gap that everyone finds so frustrating is not a mystery. It is the entirely predictable consequence of approving the direction without funding the journey.

What is currently being funded in your organisation that the strategy has deprioritised, and who has the authority and the will to change that?

Next time, we look at Closing the Gap Between Plan and Practice.

If this resonates, you will find a deeper exploration of how to see business situations clearly in The S.T.A.R. System: Applying Visual Thinking for Career & Business Success, available on Amazon.

Ai Yat Goh is the co-author of The S.T.A.R. System: Applying Visual Thinking for Career & Business Success(Marshall Cavendish Business, with Sherrie Low). Follow Ai Yat on LinkedIn and Medium.

VisualThinking #Transformation #StrategyExecution #Leadership #FromNoiseToClarity

BK HAN Candy Chan RH Malini GOW Hui Yian Germaine Kwek Joelynn Koh Lawrence Lee