Who Is the Plan Actually For?
Cover image by StockCake
The uncomfortable sociology of the programme plan, from someone who builds them for a living.
I honestly couldn't tell you how many project or programme plans I have produced over my career. Proper ones. Dependencies mapped, milestones sequenced, risk registers attached, the works. And somewhere along the way I noticed something that doesn't get pointed out in a steering committee or status meeting, almost no one reading the plan is reading it to find out what will happen.
They are reading it to find out something else entirely, if they are reading it at all.
Three audiences, one document
Every programme plan I have ever written has served at least three audiences, and only one of them cares whether it is accurate.
The sponsor reads the plan to manage anxiety upwards. Their question is not "is this right?" but "can I stand behind this in front of people more senior than me?" A plan that is honest but alarming fails that test. A plan that is confident and wrong passes it, at least until month five.
Or the dashboard built off the plan, anyway.
The steering group reads the plan to allocate accountability in advance. When something slips, and something always slips, there needs to be a document that already says whose slip it was. The plan is an insurance policy against future blame, purchased before anyone knows what the claim will be.
The delivery team reads the plan as a negotiating instrument. It is the only artefact that makes dependencies visible to people who would otherwise assume everything is possible simultaneously. "We cannot start the mobile phase until the integration layer is stable" carries no weight in conversation. Put it on a plan with a line connecting two boxes and suddenly it is real.
Accuracy is a fourth concern. It is rarely the one that shapes how the plan gets built, reviewed, or defended.
The dates that get scrutinised are not the dates that matter
Here is a pattern I have watched play out across sectors, clients, and platforms. The dates that receive the most scrutiny in plan reviews are the politically significant ones. The launch date. The date the sponsor mentioned to the board. The date attached to someone's bonus.
The structurally significant dates, the ones the entire programme actually pivots on, sail through review unexamined. The date the specification needs to be complete. The date the client team needs to have hired the content editors. The date the third-party API documentation was promised. These dates carry the whole plan on their backs, and they get thirty seconds of attention because no senior stakeholder's reputation is attached to them.
Until, of course, they slip. At which point everyone discovers, with apparently genuine surprise, that the launch date was never the load-bearing one. It's the number the equation spits out, not the variable the maths was based on.
The dependency nobody wanted to write down
The riskiest item on any programme plan is usually not the one with the red flag next to it. The red-flagged risks are the socially acceptable ones. The ones everyone already agrees are risks, which is precisely why flagging them costs nothing.
The riskiest item is the one that never made it onto the plan at all, because writing it down would have started an argument. The dependency on a team that reports into a different director. The assumption that a decision-maker who has not attended a workshop in six weeks will suddenly become responsive. The quiet reliance on one person who is visibly heading for the exit.
A programme plan is, among other things, a record of which arguments the organisation was willing to have. The gaps are a record of the arguments it was not.
I find this more useful than depressing. If you want to know where a programme will actually struggle, do not read the risk register. Read the plan for what is conspicuously absent, and ask why nobody wanted it in writing.
So do we stop planning? Obviously not
This is the point where someone usually arrives with the tired conclusion that plans are worthless and we should all just embrace uncertainty, ideally while quoting a military strategist. I have no patience for that either. Refusing to plan is not sophistication. It is just moving the arguments even later, to the most expensive possible moment.
The plan is not the problem. The pretence is the problem. The pretence that the plan is a prediction, when everyone using it knows it is a negotiation.
Once you accept that the plan is a social document, you can make it a better one. And that changes some of the strangely persistent beliefs we carry about plans, that they should be perfect from the start, that changing them is evidence of failure, that precision and confidence are the same thing.
Let those ideas go and people become much more willing to be honest. The plan can evolve as knowledge grows, which is surely more useful than maintaining a version of reality everyone has already stopped believing.
You stop optimising for false precision, the plan with 400 lines and end dates calculated to the day for work starting in eleven months. Nobody believes those dates, including the person who typed them, and everyone involved spends effort maintaining a fiction. You start optimising for shared understanding of trade-offs instead. Fewer lines. Honest ranges where ranges are honest. Dependencies stated in language a director will actually read.
You put the awkward dependency in writing precisely because of the argument it starts. That argument, had in month one across a planning document, costs a tense meeting. The same argument in month seven costs a replan, a commercial conversation, and a certain amount of trust that does not come back at the same exchange rate.
And you review the plan by asking a different question. Not "are these dates still right?" but "which of these lines is doing political work, and which is doing structural work?" The two are rarely the same lines, and confusing them is how programmes end up defending a launch date while the foundation quietly disintegrates underneath it.
The honest version
The best plan review I was ever part of did not begin with the milestones. It began with someone senior asking, "what's not on here that we're all thinking about?" The silence lasted about four seconds, which in a steering committee is roughly the length of the Third Age in Middle Earth (IYKYK). Then somebody named the thing. The plan changed that day, and the programme was better for it in ways the original document never could have delivered.
That question is available to anyone. It costs nothing except the comfort of pretending the document on the screen is the whole story.
So the next time a plan lands in front of you, by all means check the dates. But also ask who it was written for, what argument it is quietly avoiding, and which unremarkable-looking line is actually holding the entire thing up.
The plan will tell you. Just not in the rows you were looking at.
Originally published on LinkedIn on 2026-07-06. Read the original article
Comments