Leading on the Forward Edge – At Work · Weekend Reflections for Leaders · Reflection: “The Plan Will Not Survive”

Every business of consequence runs an annual planning cycle. Six to ten weeks of building, defending, and finally approving a set of numbers, followed by twelve months of reporting against them.

Every senior executive who has sat through more than two of those cycles knows the plan will not survive the year intact. We know it while we are building it. We say it out loud in the hallway. And then we run a twelve-month operating rhythm that quietly assumes otherwise.

That gap between what we know and how we operate is where the damage lives.

The failure is not that the plan turns out to be wrong. Plans are forecasts, forecasts are wrong, and being wrong at month four is not a leadership problem. The failure is having no honest cadence for re-planning. Absent one, the difference between the plan and reality does not get discussed. It gets absorbed, privately, by the people closest to the work, who patch the gap with extra hours, borrowed resources, pulled-forward revenue, and deferred maintenance. They are not hiding anything. They are doing exactly what our operating rhythm asks of them, which is to report against a number they no longer believe.

Then it surfaces in month nine, all at once, as a crisis. And the conversation becomes about accountability rather than about what we learned, which teaches everyone in the building to absorb the next gap a little longer.

Part of the fix is separating two things an operating plan is actually for, because we routinely collapse them into one document and then wonder why revising it feels like a failure of nerve.

The first is allocation: What we fund, what we staff, what we say no to. Allocation is a set of bets made with the information available in October. New information should change it. Refusing to re-allocate as the marketplace continues to grow in complexity and uncertainty is not discipline; it is the appearance of discipline purchased at the cost of the business.

The second is alignment: What we are trying to become, who we serve, what we will be known for. Alignment should be far more stable than allocation. It is the thing the team steers by when the numbers move.

When these two get fused, every change to the numbers feels like a change to the identity of the company, so leaders defend the plan long past the point of belief. Separate them, and re-allocating becomes a normal act of management rather than an admission.

Here is a practice worth installing: a standing Ninety-Day Re-Plan. Half a day, once a quarter, with the operating team. The first agenda item is not the variance report. It is a single question, answered by every function in writing before the meeting: what do we now believe that we did not believe ninety days ago? Customer behavior, competitor moves, cost inputs, what the pipeline is actually telling us, what our own execution has proven we can and cannot do. Only after that question is fully answered does anyone open the numbers.

Three disciplines that make it work:

1. Put the belief change before the variance report. If the numbers go first, the meeting becomes a defense of the numbers and the learning never surfaces. Beliefs first means people arrive prepared to say what changed rather than prepared to explain a shortfall. The order of the agenda is not a detail; it decides what follows.
2. Require every function to declare its own gap before anyone else does. The finance team should not be the first to identify the operations gap. Whoever is closest to the work names their own gap first, in their own words, with what they now recommend. In having worked with operating teams through many plan cycles, I have experienced that people will volunteer a problem early if the system reliably rewards early disclosure, and will bury it if the system punishes the messenger even once. The rule is worth stating out loud: the gap you raise in April is a data point, and the same gap raised in September is an incident.
3. Re-allocate something every quarter, even when performance is fine. If nothing moves at four consecutive re-plans, the exercise has become a ritual and everyone can tell. Move money, move headcount, kill a project, fund a small bet. The point is not the size of the change. It is proving to the organization that the plan is a living instrument, so that when a real change is needed in month five, nobody has to be brave to propose it.

No operating plan survives contact with the market. What survives is a team that has practiced re-planning often enough that doing it under real pressure is routine and that is what allows us to build a long-term healthy business rather than a well-defended forecast.

If I were to ask you, "What is the most difficult leadership challenge you are facing today?" what would you say?

Please reach out if I can help you today. My mobile is 269-370-9275 and my email is david@harvesttimepartners.com

Please download some FREE resources at www.harvesttimepartners.com

This reflection builds on two earlier Weekend Reflections for Leaders posts: Operating Plan Development and Execution and Leading Through Uncertainty (Part VIII – Resilience).

Questions this reflection answers

What is a Ninety-Day Re-Plan?

It is a standing half-day meeting each quarter with the operating team. Before the meeting, every function answers one question in writing: what do we now believe that we did not believe ninety days ago? Only after that question is fully answered does anyone open the numbers or the variance report.

Why do annual operating plans fail?

The plan being wrong is not the failure; forecasts are wrong. The failure is having no honest way to re-plan. The gap gets absorbed quietly by people closest to the work, then surfaces in month nine as a crisis. Separating allocation from alignment makes changing the numbers normal management.