The Difference Between Change Management and Change Leadership
"We already have change management. We have a whole workstream for it."
I hear this often, usually early in a first conversation, and it is almost always true. There is a plan. There is governance. There is a communications calendar with dates in it and an owner for each one.
And the reason we are talking is that none of it has produced the thing it was built to produce, which is people working differently.
The two words get used as though they mean the same activity. They do not. Understanding the difference is usually the fastest way to work out why a well-run programme is not landing.
What Change Management Does Well
Change management, in the classical sense, builds the machinery of a change. Impact assessments. Stakeholder maps. Training schedules. Communication plans with owners and dates. A structure that says who is affected, what they need to know, and when they will be told.
This work is genuinely valuable and it is often done well. In large organisations it is the only thing standing between a complex change and chaos. If your programme has three thousand affected employees across four countries, you need somebody tracking who has been trained and who has not.
What it is designed to produce is coverage. Everyone informed, everyone trained, every group accounted for. That is a real outcome and it can be measured, which is why it dominates the reporting.
Sandra (name changed, details adjusted) ran exactly this kind of workstream at an insurance company, and she ran it to a very high standard. Ninety-four percent training completion. Communications delivered on schedule to every affected population. When I met her, she was frustrated in a way that took her a while to put into words.
Eventually she said it plainly. "I can prove everybody was told. I cannot prove anybody changed."
That sentence is the whole distinction.
What Change Leadership Does Instead
Change leadership works on the decision each person makes about whether to come with you. That decision is made privately, in the days after the announcement, and it is made largely on the basis of who is asking and whether they seem to mean it.
It shows up in places no plan reaches. The team lead who explains the change in their own words rather than reading the slide, because they have understood it well enough to translate it. The senior manager who says out loud that a piece of this is going to be difficult, which tells everyone listening that honesty is permitted here. The executive who answers the question about job security directly instead of returning to the benefits case.
The work behind this is unglamorous and mostly conversational. Getting a leadership team to agree on one version of why this is happening, rather than eight overlapping ones that sound similar in the room and contradict each other on the floor. Finding out what the middle managers actually believe, as opposed to what they say in the steering meeting. Naming the fear that everybody has and nobody will raise, which in most organisations right now is some version of whether this change eventually removes their role.
None of that appears on a dashboard. All of it decides whether the training completion figure was worth anything.
The two belong together. Build the machinery without the leadership work and you get documented indifference: everybody informed, nobody moved. The reverse case is rarer and it fails differently. Real commitment builds in one part of the business and never reaches the other four thousand people, because nothing was ever built to carry it there. Most organisations I work with have invested heavily in the machinery and assumed the rest would happen on its own.
Which One Your Situation Needs
A rough diagnostic, and one I use in first conversations because it settles the question quickly.
If your problem is that people do not know what is happening, when it is happening, or what is expected of them, you have a change management problem. Build the machinery, or fix the machinery you have. More communication genuinely will help, and a specialist programme consultancy will do this better than I will.
If your problem is that people know exactly what is happening and are not doing it, more machinery will not help. You can run the training again. Completion will go back up. Behaviour will not.
The confusing cases are the ones where both are true at once, and they are common. The usual pattern is that the machinery was built correctly, the information reached everyone, and somewhere in the middle layer the change met a manager with competing pressures and stopped there. From above it looks like a communication failure, so more communication gets sent. From below it looks like something that was announced and then never mentioned again.
There is a question worth asking your own leadership team before deciding which problem you have. Ask each of them, separately, to explain in two sentences why this change is happening, without using the benefits case.
If you get one answer in different words, your machinery is the thing to work on. If you get several genuinely different answers, no amount of communication planning will fix what is coming, because the people meant to carry the change have not yet agreed on what it is.
Change management consulting for the people side of change, working with leadership teams in Zürich and across Switzerland: www.thechangerepublic.com/change-management
Tünde Lukacs is an executive coach and founder of The Change Republic. She works with senior leaders across Switzerland and Europe on leadership development, team performance, and organisational change.