Why your resource plan is wrong before you even finish writing it

I’ve sat in a lot of rooms where the plan looked completely reasonable and the delivery looked nothing like it. After a while, you start to notice that the gap is always in the same place, for the same reasons. It does not seem to matter what industry the organisation is in, how experienced the team is, or how rigorous the planning process was.

The project was signed off. The resources were allocated. The timeline was agreed.Everyone nodded. And then, somewhere between that room and the actual delivery of the work, something shifted. By the time anyone noticed, the gap had grown large enough to be expensive.

Most people assume this is a communication problem, or a culture problem, or that the wrong people were in the room. I have come to think those explanations miss the point.

It is a data problem.

And until organisations understand that, they will keep having the same conversations about why their plans do not work out.

Two rational people, two different realities

Here’s what’s actually happening when strategy and execution drift apart.

At the strategic end of an organisation, the people setting direction are working from ambition. Their job is to commit to outcomes, to drive the organisation toward goals, and to believe that those goals are achievable. But some optimism isn’t a bias we need to correct, it’s a requirement of the role. You can’t lead an organisation somewhere it’s never been by being cautious about whether it can get there.

At the delivery end, the people doing the work are operating from experience. They’ve been through enough projects to know that things take longer than expected,dependencies get missed, and estimates made in a planning meeting rarely survive their first contact with reality. They don’t add contingency because of pessimism, it’s professional caution (learned the hard way).

After all, we’d all agree that it’s what a responsible project manager does.

These two positions are both rational. Each is an intelligent response to the information they have. The problem is that they are not looking at the same information. The executive sees what the organisation wants to achieve and how much has been committed to it. The project manager sees what the work actually involves and what could go wrong. Somewhere in the middle is the truth, and neither side has full access to it.

I call this ‘reality distortion’: the gap that opens between the optimism of ambition and the caution of experience. It compounds with every planning cycle,because the mechanism that would correct it is almost never in place.

Why the reality distortion gap keeps getting wider

Most organisations plan the same way every year. Targets come down from the top.Teams build their estimates from the bottom. Somewhere in the middle, a number gets agreed and a timeline gets set.

The plan is finished. Execution begins.

What rarely happens is a systematic comparison of what was planned against what actually occurred. Not at the end of a project, in a lessons-learned session that nobody reads. I mean a continuous, disciplined process: record what was forecast, track what actually happened, and bring that data into the next planning cycle.

Without that loop, the optimism at the top is never tested against delivery reality.The caution at the bottom is never validated or corrected by evidence. Both sides are reasoning from assumptions that have never been checked, and the gap between them doesn’t close. It accumulates.

I have a phrase I use for planning that happens without actuals: dream analysis.

You’re not analysing your organisation. You’re analysing a version of your organisation that exists only in your assumptions. The plan you build from that analysis will be wrong in predictable ways, and you will not know which ways until the damage is already done.

How do we actually close the gap?

The conventional advice for fixing the strategy-execution gap is usually some version of 'communicate better' or 'get leadership aligned.' I understand why people say this, and I am not suggesting that communication doesn’t matter. But I have seen well-aligned leadership teams fail to close this gap, and I have seen organisations with imperfect alignment close it, because the difference wasn’t the quality of their conversations. It was the quality of their data.

When both sides of an organisation are working from the same picture, the distortion on both sides begins to correct itself.

The same picture means: what was planned, what is currently forecast, and what has actually happened.

The executive whose targets are consistently tested against delivery data begins to calibrate. The project manager whose estimates are regularly compared to actuals builds confidence that the data supports them. The gap doesn’t disappear, and that should never be the goal. Planning with humans will never be perfectly accurate. But the gap does become visible and manageable rather than structural and hidden.

The mechanism that makes this possible isn’t complicated.

It is a consistent process for capturing actuals: time spent, work completed,resources consumed, connected back to what was originally planned. Timesheeting tends to get positioned as an administrative burden, which is probably why it encounters so much resistance. The more accurate framing is that it’s the instrument through which an organisation measures the distance between its plans and its reality, and learns to close it.

Think of it this way. Your baseline is what you committed to: the scope, the resources, the timeline. Your forecast is your current best estimate of where things will end up, adjusted for everything that has happened since. Your actuals are what really occurred. Comparing baseline to actual is not a performance management exercise. It is how an organisation improves its ability to plan accurately over time. Without actuals, every new plan starts from the same uncorrected assumptions. The same mistakes repeat. The same gap opens.

Start with this question

When I work with organisations on their portfolio management, I often ask one question early on: when did you last compare a completed project's actual delivery to the assumptions that were made when it was planned? Not the budget variance, not whether it delivered on time. The deeper question is whether the original resourcing assumption was right, and if not, where it went wrong.

Most organisations do not have a good answer. The data is not collected in a way that makes the comparison easy. The lessons are captured in documents that do not inform the next planning cycle. The gap between strategic ambition and delivery reality is felt, discussed, and managed around rather than closed.

The fix is not a new methodology. It is not a leadership off-site. It is a consistent, unglamorous process of measuring the distance between what you planned and what actually happened, and building that data into how you plan next time.

Organisations that do this well narrow the gap. Organisations that do not keep measuring it by the results they do not get.

‍