Strategy execution fails in the gaps between functions

Integrated execution, boundaries, and the design problem most organisations have never solved.

Strategy rarely fails because individual functions are incompetent. It fails because the organisation cannot act as an integrated organisation when the situation requires it, across the structural boundaries that separate its parts. That is a different problem from alignment, capability, or even execution in the usual sense. And it needs a different kind of answer.

Strategic options do not stay open and wait for you to act. Even when your organisation has correctly read the environment and identified a viable move, that move exists within a window of opportunity. The conditions that make it possible are not permanent. A competitor's position shifts. A regulatory moment passes. A technology reaches viability and then gets commoditised. A partnership that could have been formed closes to someone else. The option was real, and then it was not, and the difference was whether the organisation could act within the required space and time.

This is a distinct problem from the question of whether you can act at all. Your organisation may have everything it needs to make a move and still fail to make it in time, not because capability was absent, but because the parts of the organisation that needed to move together could not coordinate their movement within the available window. That is the execution problem this looks to address.

The shape of the problem

Most organisations assume that if the parts work, the whole will follow. Give each function its objectives, hold them accountable, and the strategy will deliver. The challenge is that each function has its own measures and its own governance, both designed to optimise the part, not the sequence. Strategic effects are not produced by functions performing well in isolation.

They emerge from integrated action across functions, where each manoeuvre in sequence creates the conditions for the next, and the whole chain arrives at the threshold at roughly the same moment. Take market entry for an example, this requires product capability at a sufficient level, sales capacity and knowledge in the right place, operational infrastructure to support volume, channels or partnerships that provide access, and enough market awareness that buyers are ready to engage. Integrated well, and you will execute the strategy and gain an advantage.

When it does not, the organisation expends effort, potentially destabilises the organisation and produces no strategic effect. The sales team enters a market that the product cannot yet support. The infrastructure is built for a volume that the sales team has not yet reached. The partnership is formed after the window for differentiation has closed. Each function did its job. The sequence failed.

Integrated execution requires sequencing manoeuvres across functions in service of a single strategic effect, within the time the environment affords. It is not coordination in the sense of meetings and updates. It is an organisational design problem that most organisations have not solved.

Why does the structure fight integration?

The problem is not usually a failure of intent or effort. It is a consequence of how the organisation has been developed.

Functional boundaries are designed to focus effort inward and filter out distractions from the outside. That is how functions develop real capability. A product function that is constantly pulled by operational concerns will not build a coherent product. A sales team that pays attention to everything except selling is a poor sales team. The boundaries are doing their job. The problem is that the same design that provides functional capability also degrades the signal on which integrated execution depends.

Each boundary creates its own logic for reading the world. The priorities within a product function are not the same as those within a sales function, and that is by design. But when a signal crosses that boundary, it gets translated. What arrives on the other side is the same information processed through a different set of priorities and a different sense of urgency. A closing market window that is obvious to the sales team becomes a feature prioritisation question by the time it reaches product. The urgency has been absorbed by the translation.

This effect compounds over time. Creating a distinction between functions does not just reflect a difference that already exists. It reinforces and deepens it. The longer a boundary has been in place, the more the language, priorities, and ways of reading a situation on either side diverge. What starts as a convenient organisational division becomes a genuinely different interpretive reality, and the boundary between them is what makes them so.

None of this means boundaries are wrong. Organisations need them. Without boundaries, functions cannot develop the coherence and capability that integrated execution depends on in the first place. The question is not whether to have boundaries, but how permeable to make them and how to coordinate across them. A boundary that is too hard will protect the function's internal logic at the cost of the signal that needs to cross it. One that is too porous will dissolve the coherence that makes the function useful. Getting that balance right and designing the coordination that works across it are design choices most organisations have never made explicitly.

The wrong response

The instinctive response when execution starts to falter is to centralise decision-making, add more approval layers, and tighten reporting. The reasoning is that if the parts are not producing the right whole, the centre can fix the issue.

This is the wrong response, and it makes the problem worse. Centralising decisions does not improve the signal. It adds more boundaries for it to cross before it reaches someone with the authority to act. The opportunity that was visible at the edge of the organisation arrives at the centre as a dashboard report, processed through several layers of interpretation, stripped of the urgency and timing that made it matter. The response that follows operates at governance tempo, not at the tempo required.

It also removes the local judgment that sequenced execution depends on. Functions closest to the situation are best placed to sense when timing is shifting and adjust accordingly. Centralising the decision removes that sensitivity from the sequence at precisely the moment it is most needed. The organisation becomes more controlled and less capable of integrated action at the same time.

What integration actually requires

Deconfliction is the baseline. Functions are not making contradictory commitments or pulling resources in opposite directions. Most coordination mechanisms can achieve this. It is necessary and nowhere near sufficient.

Synchronisation is about timing, not just avoiding conflict. The effect only materialises when the parts arrive together. A sales team in a market without product support has not failed at coordination. It has failed at timing. And timing is not a detail of execution. It is what determines whether the effect happens at all.

Integration goes further. The parts are not just synchronised. They are mutually enabling, designed so that each creates the conditions the next requires. The whole produces an effect none of the parts could produce alone.

Effects-based orientation holds this together. You are not tracking whether each function has delivered against its plan. You are observing what change in the environment the sequence is designed to produce, and holding that constantly against what the situation is actually showing. When the environment changes, the question is not whether the plan was followed. The question is whether the actions still point to the right effect.

None of this works without shared situational awareness across the organisation; each part requires sufficient orientation of the current situation to adjust its timing relative to the others without waiting for central instruction. It is not about everyone knowing the strategy document; it's each part reading the same situation well enough to move coherently within it.

What most organisations have is deconfliction, managed through governance, running at governance tempo. What integrated execution requires is all four, designed into the operating model, running at the tempo the environment demands.

Strategy Fails in the Gaps Between Functions

Most leadership teams can describe what each function is working on. Few can describe the sequence those efforts are supposed to produce, what effect that sequence is designed to create in the environment, and how long the window for that effect remains open.

This is a fundamental gap that needs addressing, not another planning exercise, but as a genuine question about how your organisation is built.

When execution lags, what happens? If the answer is more oversight, tighter reporting, decisions pulled upward, the organisation is applying the control reflex to a structural problem. The sequence does not get better. It gets slower, and the window gets shorter.

The harder question is whether the organisational design you have is capable of the kind of integrated action the strategy requires. Not whether the functions are competent. Not whether people understand the direction. Whether the parts can move together, across their boundaries, at the tempo the situation demands, with enough shared orientation that each knows how to adjust when the environment shifts.

If you cannot answer that with confidence, the strategy may be sound, and the execution will still fail. Not because of what anyone decided. Because of how the organisation is designed.