The plan is almost never the problem.
We get shown a lot of plans. Most of them are sound. Someone has thought hard about what the business needs to change, put it in a deck, and got agreement in the room. Twelve to eighteen months later, when I ask how it went, the answer has the same shape almost every time: we got partway, then things got busy.
Nobody made a decision to stop. That is what makes this hard to see coming.

Who you gave it to
Think about who ends up owning a change programme. It goes to the person who understands the operation best. Your ops manager, your finance lead, the one who knows why the process is the way it is and where the bodies are buried. Handing it to anyone else would be negligent.
That person also has a full-time job. Their real one. The one with the month-end close in it, the customer escalation, the two people who resigned in March.
So the change work becomes an extra line on their plate. And an extra line on a full plate does not compete on merit. It competes on urgency, and it loses to everything, every week, because nothing on the roadmap is ever due today and everything in the day job is.
How it actually dies
It is never dramatic. The steering meeting moves from fortnightly to monthly because everyone is stretched. Then it moves to "we'll pick it up after the busy period", and the busy period turns out to be the year. A workstream gets parked to free someone up for something urgent, which is the correct call in the moment and every time after that.
Then the person who owned it takes a new role, or leaves, and the context goes with them. What is left is a document nobody feels ownership of and a quiet agreement not to bring it up.
I want to be clear that this is not a story about people being slack. It is the opposite. It happens precisely because the people involved are good at their jobs and their jobs keep needing them. Your best operator being too valuable to release is not a dysfunction — it is what a business under load looks like.

Why more discipline doesn't fix it
The standard response is governance. More structure, tighter reporting, a steering committee with teeth.
That treats it as a willpower problem. It is a capacity problem. You cannot fix a capacity problem by scheduling it more firmly, and the reporting layer usually makes it worse — now the person who has no time to do the work also has a status update to write about not having done it.
The other response is to hire for it. Sometimes right. Often it means a nine-month search for someone who then needs a year to learn an operation your existing team already knows, which is a long time to wait to start.
What has to be true instead
For the work to move, it has to be somebody's actual job rather than an extra line on somebody else's. That is a structural point, not a sales one, and there are a few ways to satisfy it. Ring-fencing a person internally and genuinely backfilling their role works. So does an outside team who does nothing else.
An Apex partnership is our version. We are inside your operation, we have named people on it, and the work moves in a month where you are flat out — because being flat out is our problem to route around rather than a reason for the roadmap to slip. There is a report every month whether or not you had time to think about it.
The second half matters as much. Because we sit inside the operation without sitting inside its politics, we can say the thing that is obvious internally and unsayable internally. Most businesses have a process nobody defends but nobody kills, and a system three people hate and one person protects. Those decisions do not need more analysis. They need somebody whose standing does not depend on the outcome.
The test
Take whatever you agreed to change this year and find the person whose name is on it. Then ask what else is on their plate and what happens to your programme in your worst month.
If the honest answer is "it waits", you do not have a plan problem. You have a capacity problem wearing a plan's clothing, and no amount of replanning will touch it.
A Rapid Insight Workshop maps where your work actually flows and what the friction costs you — including which parts of it have been waiting on somebody's spare time for a year.




