Govern transformation like a project.
You’ll get project outputs.
A CEO said this to me recently.
“Rob, we’re spending millions each month,
but margin hasn’t moved in two years.”
The room full of senior leaders went still.
The CFO looked up at the on-screen dashboard.
Every status box was green.
She turned to the project sponsor and said:
"...and so how has this changed our numbers?"
Projects were completing on schedule.
Teams were celebrating milestones.
The business had little to show for it.
That comment stayed with me.
Because it’s a common pattern
in medium and large organisations.
There’s plenty of activity.
There’s no shortage of delivery.
But enterprise transformation remains thin.
The issue usually isn’t effort.
It isn't a lack of commitment.
It’s the governance model.
Boards often govern transformation
like an infrastructure build.
Stage gates. Milestones. Fixed scope.
That works when the asset is known.
It fails when the capability
must be discovered and built.
Projects and programmes matter.
They’re the scaffolding of transformation.
But scaffolding isn’t the building.
Transformation works differently.
Priorities shift as evidence emerges.
Value takes time to build.
Capabilities often take longer.
What matters most isn’t deliverables.
It’s whether your organisation can perform
in a new way.
One client completed 94% of milestones.
The dashboard looked outstanding.
Green everywhere.
But operating margin stayed flat.
You have the project and programme frameworks.
What transformation framework are you using?
This is why the most impressive transformations
I’ve seen at scale create a TMO.
A Transformation Management Office.
The TMO isn't an executive committee.
It's the governance executives operate within.
It governs outcomes, not tasks.
It rests on a defined set of structural capabilities,
not a steering rhythm or a stage-gate calendar.
Learning isn't treated as deviation.
It changes what gets funded next quarter.
The first practical shift is clear.
Appoint one chair accountable
for capability and value creation.
The goal was never to finish projects.
It’s to change what your organisation can do.
What’s stopping your organisation
from governing transformation
as a system rather than a project?
Get The Boardroom Brief
Insights for leaders shaping transformation
https://cxo.fm/news
Second, an outcome-focussed pattern like STORM should make sure you are delivering on the objectives of the transformation. If the intent is to capture 10% more of a market, it's superb to be delivering projects/programmes on time, on spec and on budget... but do they lead to the desired effect in the market?
With apologies if these kinds of things were in your previous posts, haven't had much time to read over the last few weeks. May 11
I see this especially in AI and transformation programmes today. Dashboards remain green, milestones are achieved, budgets are consumed, yet the operating model underneath barely changes.
Because projects optimise for completion.Transformation optimises for new organisational capability.
That is a fundamentally different governance challenge.
The important shift in your post is the move from governing tasks and timelines toward governing learning, adaptation, capability, and measurable business outcomes.
“Scaffolding isn’t the building” is a particularly strong way to frame it. May 11