← All papers

Enterprise Strategy · Decision Integrity series

Designing an Operating Model That Executes

Strategy rarely fails in the boardroom. It fails in the wiring of who decides what, with what information, by when.

Strategy rarely fails in the boardroom. It fails in the operating model – the wiring of who decides what, with what information, by when. Most operating models are org charts pretending to be answers. This paper makes the case for treating execution as a design problem, and shows where the real fault lines lie.

Strategy Sets Direction. The Operating Model Determines Whether It Arrives.

When a strategy fails, the inquest usually focuses on the strategy itself – the market was misread, the thesis was wrong, the ambition was too great. Sometimes that is true. Far more often the strategy was sound and the organisation was simply unable to execute it, because the operating model underneath it was never designed to carry the load.

Strategy sets direction. The operating model determines whether direction becomes action. And most operating models, examined honestly, are not designed at all. They are org charts – boxes and reporting lines – presented as though structure were the same thing as execution. It is not.

An org chart answers one question: who reports to whom. An operating model has to answer harder ones:

  • Who decides what?
  • With what information?
  • By when?
  • Who is accountable when the decision is made, and when it is not?

Structure is the least interesting part of that answer. The interesting parts are decision rights, information flow, and accountability. These are precisely the parts that reporting lines leave undefined. Organisations that conflate structure with operating model design are building the roof before the foundation.

The Operating Model Gap

Most organisations have a strategy document and an org chart. Very few have a deliberately designed answer to how decisions get made, who owns outcomes, and how information moves. That gap is where strategies go to die.

The Three Fault Lines: Where Operating Models Break Down

When strategies stall, the post-mortem almost always leads back to the same structural gaps. Three fault lines account for the vast majority of execution failures – not market misjudgement, not lack of effort, but design failures buried in the wiring of the organisation itself.

Decision Rights: The Silent Friction

In many organisations the real reason things move slowly is not incompetence or resistance; it is ambiguity about who is actually allowed to decide. Choices drift upward because no one is certain they own them, or they stall because two functions both believe they do. A well-designed operating model makes decision rights explicit – this decision sits here, at this level, with this escalation path – and in doing so removes an enormous amount of silent friction.

Information Flow: Authority Without Visibility

A decision right is worthless if the person who holds it cannot see what they need to exercise it. Operating models fail quietly when authority and information are held in different places – when the person accountable for an outcome is dependent on numbers owned by someone with no stake in it, delivered on someone else's timetable. Designing the model means designing the flow: making sure the decision and the data required to make it arrive in the same hands, at the same time.

Accountability: The Shared Ownership Trap

It is common to find outcomes that everyone influences and no one owns. Shared accountability, past a point, is the same as none – because when everyone is responsible, the review meeting dissolves into an explanation of why the outcome was someone else's dependency. A model that executes assigns outcomes to individuals clearly enough that, when performance is examined, there is no argument about who was responsible for what.

Decision Rights in Practice

The matrix organisation is so often blamed for organisational slowness. Yet the matrix is rarely the problem in itself; the problem is a matrix in which no one has specified who decides when two lines disagree. Hierarchy, geography, function – any of these can create productive tension when decision rights are explicit. The same configurations become paralysing when they are not.

What Goes Wrong Without Them

  • Decisions escalate unnecessarily to the centre, creating bottlenecks at senior level
  • Two functions pursue conflicting paths because both believe they have authority
  • Choices are deferred indefinitely – not rejected, simply never made
  • Leaders spend disproportionate time in alignment meetings rather than deciding
  • Front-line managers act cautiously, uncertain of their mandate

What Explicit Rights Enable

  • Decisions are made at the appropriate level, by people with the relevant context
  • Escalation paths are clear, predictable and used only when genuinely needed
  • Cross-functional conflict has a defined resolution mechanism
  • Speed increases not through urgency, but through the removal of ambiguity
  • Accountability becomes possible because ownership is traceable

Making decision rights explicit feels uncomfortable because it requires resolving political ambiguity. That discomfort is a reliable signal that you are designing something real.

The organisations that avoid it pay for the avoidance later.

Information Flow: The Invisible Architecture

Information flow is unglamorous work, and it is where much of the real leverage in operating model design sits. The question is deceptively simple: does the person who owns the decision have access to the information they need to make it well, when they need to make it? In practice, the answer is frequently no – and the gap is structural rather than technical.

Authority and Information in Different Places

The most common failure mode: the person accountable for an outcome is dependent on data owned by a function with no stake in that outcome, delivered on a timetable set by someone else entirely. The operating model design question is not merely who has access to a system – it is whose agenda, cadence and incentives govern when and how information moves.

Designing the Flow, Not Just the Rights

Correcting this requires deliberate design of information pathways alongside decision rights. For each significant decision type, the operating model should specify:

  • what information is required,
  • who produces it,
  • at what frequency, and
  • in what form it reaches the decision-maker.

This is painstaking to document but transforms execution velocity, because it eliminates the negotiation that currently precedes every significant choice.

Accountability That Is Actually Accountable

This is where many operating models are weakest, and where the design challenge is most politically charged. Clarity about who owns an outcome requires naming individuals rather than functions, distinguishing primary accountability from contributing roles, and accepting that single ownership sometimes sits uncomfortably with collaborative culture. The discomfort is real but the alternative is worse.

When everyone is responsible, the review meeting dissolves into an explanation of why the outcome was someone else's dependency. Shared accountability, past a point, is indistinguishable from none.

Designing for Genuine Accountability

A model that executes assigns outcomes to individuals clearly enough that, when performance is examined, there is no argument about who was responsible for what. That clarity must extend to the boundaries of the role:

  • What does the owner control directly?
  • What do they influence?
  • What are the dependencies they are entitled to call upon?

The review cadence matters enormously here. Accountability without a structured moment of reckoning is merely aspiration. The operating model should specify not only who owns what, but when performance against outcomes is examined, by whom, and with what consequences – not as a punitive exercise, but as the mechanism that makes ownership real.

The Accountability Design Test

For any significant outcome in the organisation, ask: if this outcome is missed six months from now, is there one person whose name appears? If the answer is a committee, a function, or a joint accountability, the design is incomplete. Shared ownership is a design choice with a known cost.

The Test That Matters: Does the Decision Get Made on Tuesday?

The test of an operating model is not whether it looks coherent on a slide. It is whether a decision that needs to be made on a Tuesday actually gets made on that Tuesday, by someone who owns it, with the information to make it well.

Run that test against a real, recent decision that went slowly – one that should have been straightforward – and the fault line usually reveals itself immediately: no one owned it, or the owner could not see what they needed, or three people owned it equally and no one felt empowered to move.

For the Chief Executive

This reframes execution as a design problem rather than a motivational one. You do not exhort your way to delivery. You wire the organisation for it. The question to ask is not "why aren't people moving faster?" but "what in the design is creating the friction?" – and then to change the design, not the people.

For the Board

Approving a strategy without probing the operating model beneath it is approving an intention. Strategy is what you decide to do. The operating model is what decides whether it happens.

A board that scrutinises strategy but not the machinery of execution is holding half a picture. The other half is sitting quietly in the wiring.

Shehryar Gilani
Shehryar Gilani, CFA FCMA MRICSFinance leader with 20+ years across UK housing and Gulf giga-projects. Leads Portfolio Management for a Public Investment Fund-backed master developer.More about Shehryar →