The difference between strategy and operating reality

A strategy that contradicts operating reality is not a strategy. It is a wish.

Two documents, one meeting

Most leadership teams write two documents and present them as one. The first is a strategy: a story about where the company is going, who it will serve, what it will stop doing. The second is a description of the organisation as it actually runs today: how fast decisions get made, what the team can actually build, who is already overloaded, what the tooling can and cannot do. When these two documents disagree, and they nearly always disagree a bit, the strategy off-site papers over the gap with confidence instead of closing it.

I've sat in the room enough times to recognise the tell. Someone presents a three-year plan with a slide titled "Become platform-led." The engineering org in that same building 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 don't 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's a real plan, with a real cost. Nobody wants to put the cost on the slide, so they leave it off and call the gap "execution risk" instead.

What operating reality actually means

Operating reality isn't vibes. It's specific and measurable: current throughput, current skill mix on the team, current tooling, current decision latency, current customer concentration, current cash runway. It's the honest answer to "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. The distance between the two is the actual plan, whether anyone writes it down or not.

Here's a concrete example. A professional services firm decides its strategy is "AI-native delivery." Good ambition. Then you look at operating reality: every AI-generated output still routes through a three-day manual QA queue before a client sees it, because nobody trusts the output and nobody has redesigned the review process to match a faster, AI-assisted workflow. The strategy says "AI-native." The operating reality says "manual review with an extra AI-shaped step." Those are not the same company. The strategy won't survive contact with that queue unless something about the queue changes first.

Why leadership teams skip the audit

Because reading operating reality out loud is uncomfortable. Writing the future is fun. Vision decks get applause. Auditing the present means standing in front of the leadership team and saying "our managers don't have four hours a week for coaching, they have forty minutes, and the strategy assumes the four hours." That's not a popular slide. Nobody gets promoted for presenting it. 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 matters. Read the operating reality first. A strategy built before anyone has looked honestly at the present is just a hope with a deadline attached.

The gap is the risk, not a rounding error

When a strategy assumes capability the organisation doesn't have, that gap isn't a manageable line in a RAID log. It's the central risk of the whole plan, and it deserves the same seniority in the conversation as the strategy itself.

Take headcount planning. 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 actually do on day one.

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 choices. What isn't legitimate is doing neither: leaving the ambitious strategy on the wall and hoping the org 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 hasn't really been approved by the board. Only the idea of it has.

What a good strategy review looks like

Flip the ratio. Spend half the review on operating reality: what's actually 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 in the room is arguing with it, should the conversation move to the future state.

It's the same discipline behind a proper U-shaped audit: go down into what's actually 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 just a guess with better formatting.

The test

Before you sign off the next strategy document, ask one question of every initiative on it: 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. If nobody in the room can answer that line, what's actually on the wall is a slide, not a strategy.