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.
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