The Plan Survives Contact With Nothing

Category: Organisations and systems A plan written for an imagined world is defended long after the real one has diverged from it.

There is an old military line — no plan survives contact with the enemy — that gets quoted with a kind of rueful wisdom, as if everyone has long since absorbed it. The trouble is that in most organisations the opposite is true. The plan survives contact with everything. It survives the customer changing their mind, the supplier slipping, the key person leaving, the assumption turning out false, the market moving under everyone’s feet. It survives all of it, untouched, while reality quietly walks off in a different direction and the plan keeps being executed against a world that no longer exists.

Consider a programme with a date on it. The date was set eight months out, in a planning session, on the basis of what was known and assumed at the time. Everyone in the room was sensible. The estimates were reasonable given the information available. The plan was, on the day it was written, a perfectly good plan.

Then the months happened. The third-party integration that was assumed to be straightforward turned out to need a rebuild. A senior engineer left and took a quarter of the institutional knowledge with him. The scope grew, as scope does, because two early decisions turned out to need three more. None of these were catastrophes. Each was an ordinary, foreseeable piece of weather. But each one moved the real position a little further from the planned position, and by month five the gap between the route on the map and the terrain underfoot had become wide enough that anyone willing to look could see it.

Nobody looked. Or rather, plenty of people saw it, but the plan kept being treated as the thing to be delivered, rather than as a guess that was now visibly out of date. Status reports were written against the original milestones. People worked late to hit dates that the underlying reality had already made impossible. The conversation in every review was about how to close the gap to the plan, never about whether the plan still described anything real. The map was sacred and the terrain was an inconvenience.

The date arrived. The thing was not done — of course it was not done; it had not been on track to be done for three months. And the surprise in the room was genuine, which is the strangest part of the whole story. Several people had known. The information had been available the entire time. But the plan had been defended so thoroughly, for so long, that the organisation had managed to march all the way to the cliff edge while still believing it was on the path it had drawn.

The Principle

A plan is a hypothesis about an imagined future, written with the information available on one particular day. The moment it is committed to, it stops being treated as a hypothesis and starts being treated as a promise. So when reality diverges — as it always does — the organisation defends the promise rather than updating the hypothesis, because abandoning the plan feels like admitting failure, and it would rather march the route it drew than the terrain it is actually standing on.

The error is not in making the plan. Plans are necessary; you cannot coordinate a hundred people around a shrug. The error is in what happens to the plan after it meets the world. It should bend. It almost never does. It hardens into a commitment the instant it is published, and from that point on every fact that contradicts it is experienced not as useful information but as a threat to the commitment — and threats get resisted, not absorbed.

What makes this so durable is that the plan stops being a description and becomes an identity. The team is the team delivering X by Y. To say that Y is no longer reachable is not heard as “our estimate was wrong,” which is forgivable and ordinary. It is heard as “we are failing,” which is neither. So people defend the date not because they believe it, but because surrendering it feels like surrendering themselves.

Why It Is Inevitable

It is inevitable because of the asymmetry between what it costs to make a plan and what it costs to abandon one — and those costs land on different people, at different times, in different currencies.

Making the plan was cheap and forward-looking. It was an act of optimism, done in a room full of people agreeing, and nobody had to admit anything. Abandoning the plan is expensive and backward-looking. It requires someone to stand up and say, in effect, the thing we have been confidently telling everyone for five months is not going to happen. That statement has a cost that the original plan never did: it admits the earlier confidence was misplaced. And because the people defending the plan are often the people who made it, abandoning it means marking their own past judgement down. That is a tax very few people volunteer to pay.

It compounds because of how commitment works in public. Once a date has been said out loud — to a board, a customer, a wider team — it acquires witnesses. The more people who have heard the promise, the more humiliating it feels to retract, and the harder everyone clings. Sunk cost makes it worse still: the further into the plan you are, the more you have already spent, and the more the spent effort seems to argue for pressing on. We’ve come this far is one of the most expensive sentences in any organisation, because it treats money already gone as a reason to spend more.

And there is a genuine cognitive trap underneath all of it. A plan, once written, becomes the frame through which everything else is interpreted. New information does not arrive on neutral ground; it arrives into a mind that already has a plan to protect. So a slipping supplier becomes “a risk we’ll manage” rather than “evidence the date is dead.” A growing scope becomes “a few extra items” rather than “a different project.” Each fact gets quietly filed under manageable, because the alternative — filing it under the plan is wrong — is the one thing the frame is built to resist. Nobody decides to ignore reality. They simply interpret each piece of it in the most plan-preserving way available, and the sum of a hundred reasonable interpretations is a fiction.

None of this needs bad people. The person defending the dead date is usually conscientious, hard-working, and entirely sincere. They are not lying about the plan; they have talked themselves into believing it, because believing it is less painful than the conversation that comes with not. That is precisely why it is so hard to stop. The defence of the doomed plan is mounted by good people doing what feels like the responsible thing.

How It Shows Up

• Status against the original milestones stays green or amber long after the underlying reality has gone red, because the report measures progress toward the plan, not the plan’s contact with the world.
• The recovery conversation is always “how do we get back on track,” never “is this track still real?”
• A date set months ago, on now-falsified assumptions, is defended as if the assumptions still held.
• Scope quietly trebles while the deadline does not move, and nobody renames the project the different project it has become.
• “We’ve invested too much to change course now” — the sunk cost argument, dressed as commitment.
• The plan is presented to outsiders with a confidence that nobody inside the team privately shares.
• The eventual miss is met with genuine surprise, even though several people could have told you it was coming for months.
• Re-planning is treated as a failure event — something that needs explaining and apologising for — rather than a normal, healthy act of staying in contact with reality.

Why It Causes Damage

The damage is not the missed date. Dates slip; the world is uncertain; a competent organisation expects that. The damage is the months spent executing against a plan everyone could see was dead, during which the energy that should have gone into adapting went into pretending instead.

Because here is what the defended plan actually costs. Every week the organisation spends marching the wrong route is a week it does not spend choosing a better one. The slip was always going to happen — the assumptions had already broken — but the time between when it became knowable and when it became admitted is pure waste. It is the most expensive kind of waste, too, because it is invisible while it accumulates. You cannot see the cost of a plan being quietly wrong; you only see it when the wrongness finally arrives, all at once, far too late to do anything cheap about it.

It also corrupts the information system around it. To keep the plan alive, the reporting has to flatter it, and so the status updates drift toward fiction, and the people reading those updates make further decisions on the basis of a position that does not exist. A defended plan does not just waste its own time; it poisons the decisions of everyone downstream who trusted it. Other teams sequence their work around a date that was never going to hold. Customers are told things that come true only in the plan, never in the world. The fiction propagates outward, and each layer of the organisation that consumes it commits a little more of its own future to a position that has already fallen.

And there is a deeper cost, slower and harder to undo. An organisation that defends its plans long past their expiry teaches its people that updating is dangerous. It rewards the optimistic report and punishes the honest one — the person who says “this date is gone” pays a price, while the person who keeps nodding along to it stays comfortable. So people stop saying it. They learn that the plan is not really a forecast to be improved but a story to be maintained, and they maintain it, right up to the cliff edge, with everyone privately knowing and nobody officially saying. You end up with an organisation that has lost the ability to change its mind, which is the single most dangerous thing an organisation can lose, because the entire point of a plan was to help it reach a goal — and the goal was never the plan.

How To Counter It

The plan does not become survivable by being made better at the start. No amount of planning rigour will stop the world from diverging; the world diverges as a matter of course. What changes things is treating the plan as a living hypothesis from the day it is born — something to be checked against reality on a cadence, and updated without shame when reality has moved.

• Say out loud, at the start, that the plan will be wrong. Not might be — will be. Name it as a best-guess hypothesis based on today’s assumptions, and write the assumptions down where everyone can see them. A plan whose assumptions are explicit can be invalidated cleanly when one of them breaks. A plan whose assumptions are hidden can only be defended or abandoned, with nothing in between.
• Review the terrain, not just the route. Most status meetings ask “are we on track to the plan?” The better question, asked regularly, is “do the assumptions the plan was built on still hold?” When one has broken, that is the trigger to re-plan — not a failure to explain away, but a signal working exactly as intended.
• Make re-planning normal and cheap. If changing the plan is a humiliating event that requires confession and apology, people will avoid it for as long as humanly possible, which is exactly the wrong incentive. Treat a revised plan as a sign of health — proof the organisation is still in contact with reality — and the revisions will arrive early, while they are still cheap.
• Separate the commitment from the estimate, and only commit to what you can hold. A date said to a board is a promise; a date in a planning spreadsheet is a guess. Conflating the two is what makes guesses impossible to update. Be slow and explicit about what you commit to externally, and keep the internal forecast free to move.
• Refuse the sunk-cost argument by name. When someone says “we’ve come too far to change now,” that is the moment to stop and ask what you would do if you were starting from today’s position, with today’s information, and none of the money already spent. The honest answer to that question is the right plan. What you have already spent is gone either way.
• Reward the person who calls the dead plan, not the person who keeps it on life support. The colleague who says “this date is no longer real, here’s what I think is” is doing the most valuable thing anyone on the programme can do. If they pay a price for it while the cheerful optimists are left comfortable, you have built a machine for marching off cliffs.

What Good Looks Like

Good looks like an organisation that plans seriously and holds the plan loosely — that puts real effort into the route while never forgetting it is walking on terrain, not on the map.

It looks like a plan with its assumptions written on the front, reviewed on a cadence, and revised the moment one of those assumptions is shown to be false — not at the deadline, when revision is merely a confession, but in month two, when revision is just steering. It looks like a team for whom “the plan has changed” is an ordinary sentence rather than a crisis, because the plan changing is what a plan is for. It looks like external commitments made carefully and rarely, and internal forecasts that move freely as the world moves, so that nobody is ever defending a date they have privately stopped believing in.

It does not look like an absence of plans, and it certainly does not look like an absence of discipline — the loose-held plan is not a vague one. It looks like the discipline pointed at the right target: not at hitting the route you drew, but at reaching the place you were actually trying to go. The strong organisation knows the difference between those two things. The weak one confuses the map for the destination, and marches.

A Reflective Question

Think of a plan your organisation is currently committed to. If you set aside everything you have already spent and every date you have already promised, and asked only “given what we now know, is this still the right thing to be doing, on this timeline?” — would the honest answer match the plan you are defending, and if not, how long have you known?