Change fatigue puts a spanner in the works – how to build a change format that lasts for years

Most change initiatives look good on day 100. But in year two, when the steering group is still meeting and employees still need reminding why – then something has gone wrong. Here is what separates change that survives from the kind that withers.

When change still has its own logo in year three

We have come across it again and again: an organisation running a "development programme" for three years with its own steering group, its own communications plan, and its own seminars. That is not a sign of success. It is a sign that the change never really landed in the line organisation.

The changes that last have stopped being projects. They have become how meetings are run, how decisions are made, how you hire. When a new employee starts, they notice the change – not because someone tells them about it, but because that is how things work here.

When the CEO gets tired of the message

There is a toxic point in every change effort. The CEO thinks "we have said this a hundred times by now". But the employees have heard it two, maybe three times. And that is usually where the communication dies.

The overarching why should stay stable. But how it is translated has to change every time the context shifts. Not on a schedule – but when something new happens in the business. We tend to see that this works out to roughly quarterly in practice, but the important thing is that it is tied to concrete examples from the operation.

An operator who can explain why a new routine actually makes their work easier – that beats ten newsletters from management.

The difference between input and decisions

We always separate two things: check-in points and decision points. If every piece of feedback from management turns into a decision-making moment, everything grinds to a halt. But if it is an ongoing dialogue instead – "what are you seeing that we are not?" – the pace can be maintained while the direction is adjusted.

Concretely: short check-ins every two weeks, 30 minutes. No status reports. Instead: what is rubbing the wrong way, what is worrying you, where are you hearing resistance? That is where the real information lives.

Decisions are made separately, perhaps once a month. With one clear ground rule: "this is input, not a directive". It sounds simple, but it is surprisingly freeing. Both for management and for the people running the work.

Durable changes can take reality

Initiatives that wither are often too rigidly defined from the start. The first time something rubs the wrong way, it becomes a failure instead of a learning. The changes that survive get adjusted along the way – without the whole initiative being called into question.

And most importantly: when the change holds, ownership has moved out of the centre. Employees can explain why in their own words, from their own day-to-day reality. They don't need someone from HR to remind them of the purpose.

Concrete takeaway: If your change initiative still feels like a project in year two – stop communicating more. Start embedding it into how the work actually gets done.