When strategy changes, organisations often focus on priorities, initiatives, and targets. Far less attention is paid to the operating model that is expected to deliver them. This can create a fundamental mismatch. The organisation sets a new direction, but continues to rely on structures, decision rights, processes, and ways of working designed for an earlier strategy. The strategy changes. The organisation does not.

Across our work with leadership teams, we often see execution problems that are initially diagnosed as issues of accountability, capability, or performance. Sometimes those diagnoses are correct. But in other cases, the deeper problem is structural: the organisation is asking people to deliver a strategy through an operating model that no longer fits. This is where friction begins.

A business may want to become more client-centric, but retain highly siloed functions that make cross-functional collaboration difficult. It may want faster decision-making, while maintaining layers of approval designed for control rather than speed. It may prioritise growth in new markets while resources and authority remain concentrated in legacy areas.

None of these issues are necessarily obvious when the strategy is being developed. They become visible during implementation. A few warning signs tend to recur:

  • Decisions repeatedly escalate because authority is unclear or sits too high in the organisation.
  • Strategic priorities depend on collaboration across functions, but incentives and reporting lines reinforce functional behaviour.
  • Teams are held accountable for outcomes without control over the resources required to deliver them.
  • Important initiatives repeatedly become stuck at organisational boundaries.
  • Leadership spends increasing amounts of time resolving coordination problems that should be handled by the operating model itself.

When these patterns persist, the instinct is often to push harder. Leaders reinforce accountability. More governance is introduced. Additional meetings are scheduled. Reporting becomes more detailed. Sometimes this improves discipline. Sometimes it simply adds another layer of complexity to an already misaligned system.

A better question is whether the operating model still supports the strategy. That requires leadership teams to look beyond the organisation chart. An operating model includes how decisions are made, how resources are allocated, how teams interact, how performance is measured, and how work moves across the organisation. The key is alignment.

If the strategy requires faster responses to clients, decision rights should support speed. If it depends on collaboration across business units, performance measures and incentives should reinforce shared outcomes. If growth depends on a new capability, resources and leadership attention should follow that priority.

These choices sound obvious. In practice, legacy structures are remarkably persistent. They carry history, status, established power relationships, and familiar ways of working. Changing them can therefore be more difficult than changing the strategy itself.

This does not mean that every new strategy requires wholesale organisational redesign. Often it does not. The goal is not to reorganise for the sake of change. It is to identify where the existing operating model materially obstructs the strategic direction and make targeted adjustments.

Leadership teams should be asking:

  • Where does our current operating model make the strategy harder to execute?
  • Which decisions need to move closer to the people doing the work?
  • Where are structures or incentives reinforcing yesterday’s priorities?
  • What organisational changes are genuinely necessary to deliver tomorrow’s strategy?

Strategy does not operate in a vacuum. It is delivered through the organisation as it actually exists. If that organisation was designed for a different set of priorities, execution problems should not come as a surprise. Sometimes the issue is not that people are failing to implement the strategy. It is that the organisation was never designed to enable it.