← Journal

Change management versus — what? Part 2

Change · 15 April 2026 · 2 min read

Change management versus — what? Part 2

A few weeks ago I wrote this:

Maybe it’s time to stop calling it Change Management and start rethinking what change really is. Because words matter. “Management” implies control, process, oversight. But can we really manage change? Because change itself isn’t the hard part. People are.

That post hit a nerve. Hundreds of comments. Loads of thoughts. Many name suggestions.

Change Leadership. Change Enablement. Change Guide. Business Improvement. People Readiness. Change Architects.

Which got me thinking - if this many smart people can’t agree on one name, maybe the name was never the real question.

Some of you pushed back hard, and rightly so. Without some rigor - ownership, sequencing, governance - leadership alone becomes chaos disguised as agility.

Others went further still. Rename the function all you want. But if decision rights don’t shift, if nobody owns the outcome after go-live, the organisation just pulls people back to the old way. Quietly.

So maybe I had it half right the first time.

Words do matter. But maybe not on their own.

What if the name isn’t the starting point - it’s the ending point?

Start with the behaviours you actually need. Who needs to decide differently? Who owns the outcome after go-live? What does “moved” really look like, six months on?

Get that right first. Then let the title follow the behaviour, not the other way round.

So, here’s where I’ve landed - for now. The name I keep coming back to is Change Enablement. It captures “creating the conditions for people to act differently” - and it still implies deliberate, structured work. Not control. Not chaos. Something in between.

Because a name chosen before the behaviour exists is just a label. A name chosen after is a description of what’s real.

What’s yours?