Why Strategy Documents don’t Survive Contact with Operations

Strategy is defined at an altitude where it is internally coherent. It connects objectives to outcomes, articulates priorities, and provides a rationale for investment decisions. At the level at which it is written, it is usually correct.

The problem is that it cannot be directly translated into the operational decisions that would realise it — which systems to invest in, which capabilities to build, how to sequence change — without a structured view of the current state.

Most strategy processes do not produce that view. That is where the gap opens.

The gap between strategic intent and operational reality is not a failure of strategy. It is a structural characteristic of how strategy is produced.

A board-level strategy document is designed to communicate direction, not to specify execution. It does not need to know which legacy systems constrain the roadmap, which organisational capabilities are genuinely available versus aspirationally described, or which existing processes would need to change to realise each objective. That translation is someone else's problem.

The translation problem is where strategies go quiet.

The document exists, the priorities are understood at the leadership level, and somewhere between board approval and operational programme planning, the strategy becomes an input that everyone acknowledges and nobody acts on with specificity.

The initiatives that get funded are the ones whose sponsors can already see the path from current state to outcome. The strategic objectives that require hard choices about the current operating model tend to be deferred to the next cycle.

There is also a specific problem with how strategy gets interpreted across an organisation. Strategy documents use language that is intentionally accessible — terms like customer-centric, operationally excellent, digitally enabled. These are designed to be understood by everyone. They are also designed to be interpreted by everyone, which means that in the absence of more specific guidance, each part of the organisation derives its own operational version of what the strategy means for them.

Two business units, two interpretations, two sets of change programmes moving in directions that are individually consistent with the strategy and collectively incoherent.

The analytical work that closes this gap is not glamorous, but it is specific. It requires mapping strategic objectives onto the capabilities the organisation currently has and the capabilities it would need to develop. It requires identifying which processes, systems, and organisational structures support the current state — and which would need to change to support the target. It requires being explicit about the sequence in which those changes can realistically be made, given the dependencies between them and the capacity constraints that determine how many things can change simultaneously.

This is, in essence, the work of connecting the strategy to the current-state and target-state analysis that makes it executable. A strategy that has been mapped onto a business capability model — showing which capabilities it requires, which exist, which need investment, and which need to be built — is a different kind of document from a strategy that has not. It can be tested for reachability. It can be sequenced. It produces decisions rather than priorities.

The organisations that execute strategy most effectively are not the ones with the most sophisticated strategic planning processes. They are the ones that invest in the translation layer — the structured analysis that connects what the strategy says to what the organisation actually is, and identifies specifically what needs to change for the two to align. That translation is where the strategy either becomes operational or stays aspirational.

A strategy that cannot be mapped onto the current state of the organisation is not yet a plan. It is a direction. The distance between those two things is what determines whether the next planning cycle looks like progress or repetition.

Next in this series: why enterprise software fails the organisations that invest most in it — and the current-state question that almost nobody asks before go-live.