Week 13: Transformation Is Not a Project. Stop Putting End Dates on It.
Transformation Is Not a Project. Stop Putting End Dates on It.
The moment you name your transformation programme, you have already started killing it.
I know that sounds extreme. But I have watched this happen so many times -- across 40+ organisations over 20+ years -- that I can almost predict the outcome from the launch announcement.
"Welcome to Project Phoenix." "Introducing Operation Excellence 2027." "The Future Forward Programme." "Horizon 3.0."
The moment the transformation gets a name, a logo, a Gantt chart, and an end date, the entire organisation does a very rational calculation: survive until it is over.
Because projects end. By definition. A project has a start date, an end date, milestones, deliverables, and a close-out. And when you frame transformation as a project, you tell every person in the organisation that this is temporary. That there is a finish line. That if they wait long enough, it will pass.
And they are right. It will.
Two Organisations, Two Outcomes
Let me tell you about two organisations I worked with. Both used the word "transformation." Both meant something completely different by it. And the difference determined everything.
Organisation A: The Programme
A large services company in the energy sector. They announced a "Business Transformation Programme" with a three-year timeline. They had everything: a programme office, a steering committee, a dedicated budget, workstream leads, stage gates, traffic-light reporting, and a programme manager whose title barely fit on a business card.
The launch event was impressive. Senior leadership committed publicly. Resources were allocated. External consultants were engaged. The programme had its own branding, its own newsletter, and its own section on the company intranet.
For the first twelve months, it delivered. Projects completed. Savings documented. Quick wins celebrated. The programme dashboard was mostly green. Quarterly reports to the board were positive.
Then something happened. Slowly, almost imperceptibly.
People started talking about the programme in the third person. "When the programme asks us to..." "What the programme wants us to do..." "Once the programme is over..." It became a thing that existed alongside the organisation, not within it. Something being done to people, not by them.
By year two, the programme was running on momentum and obligation rather than conviction. Teams completed programme deliverables because they were mandated, not because they believed in them. The quality of improvement declined. The creativity disappeared. It became compliance.
By year three, the programme officially "completed" on schedule. The close-out report showed impressive numbers. Savings targets met. Projects completed. Milestones achieved.
Within six months of close-out, nearly 40% of the improvements had reverted. Because the programme was over. The mandate was gone. The programme office was disbanded. And the organisation went back to how it had always worked.
Three years. Millions in investment. And less than two-thirds of the improvements sustained.
Organisation B: The Culture
Shell Malaysia. Different approach entirely.
There was no "programme." No launch event with a name and a logo. No three-year timeline. No end date. What there was: an operating rhythm. A set of daily, weekly, monthly, and quarterly disciplines that became how the operation ran. Not something extra. Not a project running parallel to the real work. The work itself.
Daily stand-ups at visual boards. Weekly improvement reviews. Monthly performance steering. Quarterly strategic alignment. Gemba walks that were part of the leadership routine, not a special event.
Nobody called it a "transformation programme." It was not referred to by a name. It was not separate from normal operations. It was normal operations. The way we work. Not a thing we are doing. The thing we are.
The improvements sustained. Not because there was a programme office enforcing compliance. Because the operating rhythm made improvement a daily habit rather than a project deliverable. When your daily stand-up includes a discussion of the improvement action, the improvement does not stop when a programme closes. Because there is no programme to close. It is just Tuesday.
The Naming Problem
I am going to be very specific about why naming the transformation is dangerous.
When you name something, you create a boundary around it. Inside the boundary: transformation. Outside the boundary: everything else. And in most organisations, "everything else" is what people actually spend their time on.
A named programme immediately creates insiders and outsiders. The programme team is inside. Everyone else is outside, observing, occasionally participating when asked, and fundamentally waiting for it to be over.
I saw this at four different organisations. The transformation programme had a dedicated team. The dedicated team was enthusiastic, capable, and hardworking. And completely isolated from the rest of the organisation, who viewed the programme as "their thing" rather than "our way of working."
When the programme ended -- and it always ended, because projects always end -- the capability left with the programme team. The rest of the organisation had never internalised the changes because the changes had always belonged to the programme, not to them.
The End Date Problem
An end date is even more destructive than a name.
When a transformation has an end date, every stakeholder does the math. Three years? I can outlast that. Two years? I can keep my head down and wait. Eighteen months? I do not even need to pretend to be engaged.
I worked with an organisation where a middle manager told me -- with remarkable honesty -- "I have been through four transformation programmes in twelve years. They all had end dates. They all ended. I just keep doing my job and they go away."
He was not being cynical. He was being rational. His lived experience was that transformation programmes are temporary. And he was right. They were.
The organisations that actually transform -- genuinely, permanently transform -- do not put end dates on it because there is no end date on "how we work."
You do not set an end date for safety. You do not say "We will be safe until 2028 and then re-evaluate." Safety is permanent. Non-negotiable. Part of the fabric.
Improvement should be the same. You do not stop improving. You do not complete improvement. You improve. Continuously. That is the entire point. The clue is in the name: Continuous Improvement. Not "Improvement Until The Programme Budget Runs Out."
What Actually Works
After watching both approaches across dozens of organisations, here is what I have learned works.
Call it what it is: how we work. Not a programme. Not a project. Not an initiative. The way we operate. The way we run meetings. The way we solve problems. The way we make decisions. When improvement is embedded in the operating rhythm rather than layered on top of it, it does not need a name, a logo, or an end date. It just exists. Like finance exists. Like HR exists. Like safety exists.
Embed the discipline in existing structures. Do not create parallel governance. Do not create a separate steering committee for the transformation. Embed improvement reviews into the existing management cadence. The monthly business review should include improvement performance. The weekly team meeting should include improvement actions. The daily stand-up should include improvement status. When improvement has its own separate meetings, it is separate from the work. When it is part of the regular meetings, it is part of the work.
Transfer capability, not dependency. The goal is not a CI team that runs improvement for the organisation. The goal is an organisation that improves itself. Every person, every team, every department with the capability and the authority to identify problems and fix them. When you have that, you do not need a programme. You have a culture.
Make the cadence the infrastructure, not the programme. I keep coming back to cadence because it is the answer to almost every sustainability question in CI. The daily, weekly, monthly, quarterly rhythm is what makes improvement survive leadership changes, budget cycles, reorganisations, and the inevitable ups and downs of organisational life. Programmes can be cancelled. Cadence, once embedded, persists.
At Shell Malaysia, the operating cadence survived multiple leadership changes. Different leaders brought different styles, different priorities, different personalities. But the cadence remained. Because it was not one leader's programme. It was the way the operation worked.
The Challenge
If your organisation is about to launch a "transformation programme," I want you to ask one question before the launch event.
What happens when this programme ends?
If the answer is "the improvements will be sustained through normal operations," ask: "What specifically in normal operations will sustain them? What cadence? What review? What accountability mechanism?"
If nobody can answer those questions concretely, the programme will deliver while it is active and revert when it is over. That is not transformation. That is a temporary project with a grand name.
Real transformation does not have an end date. Because real transformation is not something you do. It is something you become.
Does your organisation have a named transformation programme with an end date? If so, ask yourself: what happens on the day after the programme officially closes? If you do not have a specific, credible answer, you already know the outcome.
Build an operating rhythm that outlasts any programme. The Stormholt Performance and Process Management Mastery course teaches the cadence that sustains, not the project that expires.
https://stormholt.org/products/performance-and-process-management-mastery