Why Change Programmes Stall After the Announcement
A COO I worked with in Zürich showed me a dashboard once. Every milestone was green. The rollout was on time, the training numbers were met, the communications plan had gone out on schedule.
Then he said the sentence I now hear in some form in almost every first conversation.
"Everything is on track. Nothing has changed."
That gap, between a programme that is running correctly and an organisation that is behaving exactly as it did before, is where most change work actually lives. It rarely shows up in the reporting, because nothing in the reporting is designed to catch it.
Where a Change Actually Dies
The announcement is the part everybody prepares for. The town hall, the slide deck, the carefully worded message about why this matters. Enormous effort goes into that moment, and it usually goes well.
What happens next is the part nobody owns.
Between the announcement and the actual work sits a layer of people who have to translate the decision into something their own team can do on Monday morning. Team leads, department heads, middle managers. They were not in the room where the change was decided. They are being measured on this quarter's delivery, not on next year's transformation. And they are now expected to sell a change they had no part in shaping, to people who will ask them questions they cannot answer.
Markus (name changed, details adjusted) was a Head of Operations at a manufacturing company in the German-speaking part of Switzerland. He supported the change. He said so in every steering meeting, and he meant it. He also protected his team from it for four months, because his numbers were under pressure and the change would have cost him throughput in the short term.
He was doing his job, exactly as his job had been defined for him.
This is the layer where most changes stop. They stop through a hundred reasonable local decisions to do the change later. Opposition would be easier to deal with, because opposition announces itself and can be answered.
Why Quiet Agreement Is the Most Expensive Response
Open resistance is a gift. Someone tells you what is wrong, and you can work with it.
What you get instead, in most organisations at senior level, is agreement. People nod in the meeting. They use the language of the change accurately. They ask no difficult questions. And then very little moves.
I have watched this happen often enough to know where it comes from. A well-run organisation trains people to behave exactly this way. Senior professionals learn early that disagreeing in the room is expensive and disagreeing afterwards is free. So the concerns go sideways, into corridor conversations and one-to-ones, where they never reach the people who could act on them.
The cost lands later, and it lands twice. The first cost is time, because a change that stalls invisibly is a change nobody escalates until the deadline is close. Credibility is the second, and it lasts longer. When the next change is announced, people remember that the last one arrived, consumed everyone's attention, and then went nowhere.
The signal to watch for is a specific kind of silence. A room with no questions usually just means people are being careful. The room that matters is the one where every question is about process. When people ask about timelines, tooling and reporting lines, and nobody asks what this means for them, they have already decided the change is something to be endured rather than joined.
What Restarting a Stalled Change Takes
The instinct, when adoption is flat, is to communicate more. Another town hall, another round of training, a stronger message from the top. It is the cheapest intervention available and it almost never works, because the problem was never that people had not heard.
Three questions do more than another campaign.
The first is where the resistance actually sits. In my experience it is rarely the front line, who tend to be pragmatic, and rarely the executive team, who decided it. It is usually the layer in between, and the reason is almost always a genuine conflict between the change and what those managers are measured on.
The second is what your honest answer is when someone asks what this means for them. People will accept difficult answers. A rollout plan offered in response to a question about someone's future is not an answer, and everybody in the room knows it. If part of the answer is genuinely still open, say that it is open, and say when it will be settled.
The third is who has to carry this, and what has been taken off their plate to make room. A change added on top of a full workload is a change that will be done last. This question separates the programmes that land from the ones that do not, more reliably than anything else I ask.
None of this is complicated. It is uncomfortable, and it takes senior attention at a point in the programme when senior attention has usually already moved on to the next thing.
A stalled change is recoverable, and it is often faster to fix than a new one is to start, because the resistance has stopped hiding. By the time adoption is visibly flat, everybody involved knows where the problem is. They are usually waiting for someone to ask.
Change management consulting for the people side of change, for 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 leadership teams across Switzerland and Europe on change that has to be carried by people, not only planned.