The difference between strategy and operating reality

A strategy that contradicts operating reality is not a strategy. It is a wish. And most leadership teams write both documents, present them as one, and never reconcile the two. Strategy vs operating reality is not an abstract distinction. It is the difference between a plan the organisation can execute and a slide it will fail to grow into.

Strategy and operating reality: two documents nobody reconciles

Sit in enough strategy off-sites and you learn to spot the tell. A three-year plan goes up with a slide titled "Become platform-led." In the same building, the engineering org still ships every client a bespoke build: no shared components, no reusable IP, a backlog of one-off requests six months deep. Nobody in the room says the obvious thing out loud. You do not become platform-led by writing the words "platform-led" on a slide. You become platform-led by funding a rebuild, freezing bespoke work for a quarter, and accepting slower delivery while the foundation gets laid.

That is a real plan, with a real cost. Nobody wants the cost on the slide, so they leave it off and call the gap "execution risk" instead. Two documents, presented as one. The first is the strategy: the story about where the company is going. The second is the description of the organisation as it actually runs today: how fast decisions get made, what the team can build, who is already overloaded, what the tooling can and cannot do. When those two disagree, and they nearly always disagree a bit, the off-site papers over the gap with confidence rather than closing it.

The confidence is the problem. A wish said firmly enough, on a good template, reads like a decision. It is not one. The same dynamic sits underneath why most change programmes fail: the ambition was never wrong, the reconciliation with the present never happened.

What operating reality actually means

Operating reality is not vibes and it is not culture. It is specific and measurable: current throughput, current skill mix on the team, current tooling, current decision latency, current customer concentration, current cash runway. It is the honest answer to one question. What can this organisation actually do this quarter, with the people and systems it has right now.

Strategy describes a future state. Operating reality describes the present state, measured. The distance between the two is the plan, whether anyone writes it down or not.

Here is the version I watch play out most often now, because everyone has the same ambition on the same slide.

That is what reading operating reality buys you. Not a mood, a measurement. You can point at the queue. You can time it. You can name the person who owns it and the reason it exists. None of that appears on the strategy slide, which is exactly why the slide is dangerous on its own.

Why the gap never makes the slide

Reading operating reality out loud is uncomfortable, and writing the future is fun. Vision decks get applause. Auditing the present means standing in front of the leadership team and saying "our managers do not have four hours a week for coaching, they have forty minutes, and the strategy assumes the four hours." That is not a slide anyone gets promoted for presenting. So most strategy processes spend ninety percent of the time on the future and ten percent, if that, checking whether the present can support it.

The order is the fix, and it is nearly free. Read the operating reality first. A strategy built before anyone has looked honestly at the present is a hope with a deadline attached. Read the present, then build the future on top of what is actually there. It is the same down-then-up discipline behind a proper audit: go down into what is happening on the ground before you come back up with a plan for where it should go. Skip the down leg and the up leg is a guess with better formatting. That sequence is the whole of the Read, Craft, Scale method: you do not get to redesign anything until you have read the grain of how work actually flows.

The reason this keeps happening is not stupidity. It is incentive. Nobody in the room is paid to be the person who slows the vision down with the truth about the present. So the truth waits, and it turns up later, at much higher cost, wearing the word "execution."

The gap is the risk, not a rounding error

When a strategy assumes capability the organisation does not have, that gap is not a manageable line in a RAID log. It is the central risk of the whole plan, and it deserves the same seniority in the conversation as the strategy itself.

Take headcount planning, the cleanest example there is. A growth strategy assumes the sales team can carry double the pipeline next year at the same headcount. Nobody checks whether the CRM data is clean enough to route leads without manual triage, whether the SDRs have the tooling to work double the volume, or whether the sales manager has ever run a team this size before. Six months in, the number gets missed, and the retro calls it execution. The retro is being kind to itself. The real failure happened months earlier, when nobody checked the strategy against what the team could do on day one.

The uncomfortable part is that closing the gap is usually cheaper and more concrete than the ambition that hid it. A strategy that assumed the organisation needed to buy its way to a new capability often turns out to need one workflow rebuilt and two people who can build it.

That number was not on any strategy slide. It was sitting in the operating reality the whole time, waiting for someone to read it. The strategy talked about the future of the tooling stack. The present held forty thousand pounds of annual spend that no living person had chosen. Reading the present did more for that plan than any amount of writing the future.

Closing the gap, in both directions

Once the gap is visible, there are only two honest moves. Fund the change in operating reality explicitly, with the time, headcount and money it actually costs to close. Or change the strategy to match what the organisation can do today. Both are legitimate. What is not legitimate is doing neither: leaving the ambitious strategy on the wall and hoping the organisation grows into it by accident, on nobody's budget, on nobody's timeline.

If the plan requires the organisation to become something it is not yet, say so on the same slide as the plan, with a number attached: the hires, the months, the systems, the training. A strategy without that number has not really been approved by the board. Only the idea of it has. The difference between a plan and a wish comes down to whether the change it depends on has an owner, a cost and a date.

Funding the change is not the same as approving a bigger budget and hoping. It is the operating intervention done deliberately: pick the one workflow the strategy actually leans on, rebuild it, and put the capability where the plan needs it before the plan needs it.

What a good strategy review looks like

Flip the ratio. Spend half the review on operating reality: what is true right now, measured, not described in adjectives. What the team can build. What the tooling supports. Where the bottlenecks already sit before you stack ambition on top of them. Only once that picture is agreed, and nobody is arguing with it, should the conversation move to the future state.

That first half is not a status update. It is a diagnosis, and it has its own signals of health worth reading properly. A team that ships small things weekly, resolves decisions without escalation, and can name who owns each critical workflow is carrying a very different operating reality from one that cannot, however similar their two strategy decks look. If you want the specific tells, signals of operating health lists what to look for and what the absence of each one costs you later.

The review that flatters everyone spends its time on the future because the future has no counter-evidence yet. The review that works spends its time on the present because the present is where the plan will actually be tested. A vision is easy to agree with. An honest read of the present is where the disagreements live, which is exactly why it is worth the room's most senior attention.

The test before you sign off

Before you sign off the next strategy document, run every initiative on it through one filter. Does the organisation, as it exists today, have the capacity, skill and tooling to do this? If the answer is no, the document needs one more line: what closes that gap, and who is paying for it.

None of this is a call to lower ambition. The organisations that pull off the hard strategies are not the ones with smaller plans. They are the ones that read their own operating reality clearly enough to know exactly what the plan will cost, and then decide, in the open, to pay it. Strategy vs operating reality is not a tension to resolve once. It is the discipline of keeping the story about the future honest about the present it has to start from, every review, every quarter. That discipline is most of what operating leadership actually is.