tgroenwals shared this post · 3d ago
Rob Llewellyn

Your project closed green.
So why does nothing feel different?

Most leaders have lived this.

The milestones hit. The budget held.
The steering committee applauded.
Yet nothing fundamental changed in the business.

Here's the uncomfortable truth.
You delivered exactly what
you were asked to deliver.

Projects deliver outputs.
Outcomes and benefits only arrive
when the business changes how it works.

That's not my definition.
PRINCE2 and the PMBOK both say it.

And there's a deeper pattern.
Most projects, not all, are focused on optimisation.
They make the existing business more efficient.
Faster processes. Lower costs. Fewer errors.
All valuable work.

But optimisation only improves the business you have.
It doesn't change the operating or business model.
Transformation does.

And both standards are honest
about what happens at closure.

The project team disbands.
Deliverables transition to the business.
Benefits realisation is handed over.

Some will say that's what a programme is for.
And frameworks like MSP are excellent there.
But a programme is still a temporary organisation.

It starts. It delivers. It closes.
Nobody failed here.

Project managers delivered the outputs.
That was their job.

Programme managers delivered the outcomes.
That was theirs.

And PMOs supported with standards,
assurance and reporting.
That was theirs.

Everyone did exactly what temporary initiatives
require them to do.

But transformation isn't temporary.

Some will push back on that, saying
transformation should have an end state too.
But here's the problem with that.

Markets shift. Technology evolves.
Customer expectations change.
Competitors don't wait.

Transformation is a recurring cycle,
not a one-off event.
Treat it as temporary
and your organisation becomes temporary too.

Because a business that stops transforming
eventually becomes obsolete.
And when every initiative closes,
the same question returns.

What's standing there to keep building
capability and value?

In most organisations, nothing.
There's no overarching,
permanent transformation structure.

HR, IT and finance are all permanent structures.
The best organisations treat transformation the same.

That's why so many organisations complete hundreds
of successful projects and still fail to transform.

They optimised what they had.
They never changed what they are.

Enterprise transformation isn't a handover.
It's the continuous building of new capabilities.
New ways of operating.
New ways of creating value.
That work never gets a closure report.

The answer isn't fewer projects, fewer programmes
or better PMOs.

It's placing them all inside
an enterprise transformation system.

A permanent structure that governs
outcomes and builds capability
long after every initiative closes.

The leaders who understand this
are those who stopped only running initiatives,
and now orchestrate enterprise transformation.

Download the TMO² Operating Model handout.
https://cxo.fm/tmo

Rob Turner, MBA This is the pattern I see repeatedly in ServiceNow implementations. The platform goes live on time and on budget, the project closes green, and within six months the CMDB data is rotting because nobody built a permanent governance structure to maintain it. Every process that depends on that data — incident, problem, change, impact analysis — is now operating on assumptions instead of facts. The project delivered the output. Nobody owned the ongoing capability. Your point about permanent transformation structures is the answer, but in my experience the resistance isn't intellectual — leaders agree with it in the room. The resistance is budgetary. Permanent structures require permanent headcount, and most organizations won't fund a transformation function the way they fund IT or finance. So the work gets re-packaged as the next project, the next program, and the cycle restarts.
Rob Llewellyn Author That’s the challenge Rob. Without permanent ownership, the cycle simply repeats.