The organisation is launching another transformation. The CEO stands in front of several hundred employees and speaks enthusiastically about the future. The presentation contains familiar promises: greater agility, stronger collaboration, simplified processes and a more customer-focused culture. The executive team expects energy. Instead, the room is quiet. Employees listen politely. Some take notes. Few ask questions. When the event ends, senior leaders describe the reaction as disappointing.

• “People are resistant to change.”
• “They do not understand the urgency.”
• “We need to work on their mindset.”

But employees understand more than leadership realises. They remember the previous transformation. They remember the steering committees, consultants and workshops. They remember being asked to complete their normal work while redesigning the organisation in the evenings. They remember the new structure that changed reporting lines without clarifying authority. They remember that difficult decisions were postponed, the executive sponsor moved to another role and the programme quietly disappeared.

No one officially said it had failed. Leadership simply stopped mentioning it. Employees learnt something from that experience: survive the launch, use the new language and wait for leadership’s attention to move elsewhere. That is not necessarily resistance to change. It is organisational memory.

The Label Protects Leadership

Calling people resistant is convenient. It places the problem inside the employee. They are fearful, negative, inflexible or insufficiently ambitious. Leadership remains progressive and future-focused. The diagnosis removes the need to examine whether the transformation itself is credible.

• Are the priorities clear?
• Has enough capacity been provided?
• Will senior leaders change their own behaviour?
• What happened to the promises made during the previous initiative?

These questions are more uncomfortable than discussing employee mindset. Some people do resist change for self-interested reasons. Change can threaten status, expertise, influence and security. Not every objection is wise, and no organisation can give every employee the right to veto necessary progress. But treating all resistance as a psychological weakness is intellectually lazy.

Pushback can contain valuable information.

Employees may see operational dependencies that senior leaders have missed. They may understand how customers will experience the new process. They may recognise that two supposedly aligned initiatives are competing for the same people. When leadership labels these concerns as resistance too quickly, it loses access to precisely the information required to make the change work.

People Remember the Costs Leaders Forget

Senior executives often experience transformation through presentations, milestones and governance meetings. Employees experience it through disrupted work. They learn new systems while old systems remain active. They attend additional meetings, manage confused customers and attempt to interpret responsibilities that leadership has not fully resolved.

When the initiative loses momentum, executives move on to the next priority. Employees remain with the consequences. They carry the duplicated processes, unfinished structures and promises that were never formally withdrawn. Years later, a new leadership team may describe the organisation as beginning with a clean page. For the people still working inside it, the page is not clean. It is crowded with previous attempts.

Organisational memory often survives longer than executive tenure. A recently appointed leader may genuinely believe the latest programme is different, while employees see another name for a pattern they already know. Their scepticism is not evidence that they oppose the future. It may be evidence that leadership has not yet distinguished this transformation from the past.

Change Fatigue Is Often Completion Fatigue

Organisations frequently say their people are tired of change. People are often more tired of incomplete change. A transformation is announced, but the old process remains. A new structure is introduced, but the previous decision rights continue informally. Leaders ask for different behaviour while preserving the incentives that produced the old behaviour. Each initiative adds another layer. New terminology is introduced without removing the old language. New reporting requirements sit beside existing ones. Employees are told to become more agile while approval processes grow. The organisation is not moving from one operating model to another.

It is accumulating both.

This creates a particular kind of exhaustion. People are not simply working harder. They are continuously switching between contradictory expectations. When the next transformation arrives, they do not assess only its potential benefits. They calculate the additional complexity it may leave behind. What leadership interprets as reluctance may be a rational response to organisational clutter. A company does not demonstrate its capacity for change by starting many initiatives. It demonstrates it by finishing them.

Understanding the “Why” Is Not the Same as Trusting the “How”

Leaders are frequently advised to communicate the reason for change. That matters. People need to understand the market pressure, customer expectation or strategic opportunity behind a transformation. But a compelling explanation is not enough. Employees may fully accept why change is necessary and still distrust how leadership will deliver it.

• They may agree that the organisation needs to become more customer-focused, yet doubt that senior leaders will surrender functional power.
• They may understand the need for greater efficiency, while expecting that leadership will remove roles before removing unnecessary work.
• They may support digital transformation, but know that the technology will be introduced without sufficient training or process redesign.

This is not a communication gap. It is a credibility gap. Credibility is not created by explaining the new programme more frequently. It is created when leadership behaves differently from the pattern employees remember. No presentation can compensate for a history of abandoned commitments.

Do Not Ask for Ownership After Everything Has Been Decided

Another common mistake is inviting employees to participate after the most important decisions have already been made. They attend workshops, place ideas on walls and answer questions about how they feel. Yet the outcome, structure and timetable are fixed.

Leadership calls this involvement. Employees recognise it as managed consent. Real participation does not mean that every decision is made collectively. Senior leaders remain responsible for setting direction and making difficult choices. It means that the people closest to the work can influence how the change is designed and implemented. Their knowledge is used before the plan becomes politically impossible to adjust.

They are told which decisions remain open, which have already been made and why. False participation is worse than no participation because it asks people to perform ownership without granting influence. If leadership wants employees to take responsibility for the new organisation, it must allow them to shape meaningful parts of it. Ownership cannot be requested after agency has been removed.

Acknowledge What Happened Before

Leaders sometimes avoid discussing previous failures because they want the organisation to look forward. This instinct is understandable. It is also counterproductive. The absence of acknowledgement does not erase the past. It simply tells employees that leadership is unwilling to discuss it. A credible transformation may need to begin with a direct statement:

• “We asked people to support a major change, but we did not remove enough existing work.”
• “We launched a new structure without clarifying decision authority.”
• “We stopped communicating when the programme became difficult.”
• “We did not follow through on several commitments.”

This level of honesty can feel risky. It also demonstrates that leadership has learnt something. An acknowledgement should not become a public exercise in blame. The purpose is to name the pattern clearly and explain what will be different this time.

• Which work will stop?
• Who will remain accountable from beginning to completion?
• What resources have been committed?
• How will concerns be escalated?
• Which decisions will be made locally?
• What will leadership do when short-term pressure makes the old behaviour tempting again?

Employees do not need an elaborate apology. They need evidence that the organisation has converted memory into learning.

The Old Organisation Must Be Allowed to End

Many transformations struggle because leadership wants the new operating model without letting go of the old one. The organisation introduces empowerment, but executives continue intervening in decisions.

• It promotes collaboration, while budgets and targets remain entirely functional.
• It asks managers to coach, while rewarding them only for immediate output.
• It launches a new process, but allows influential people to bypass it whenever it becomes inconvenient.

Employees watch these exceptions closely. They reveal whether the transformation is real or temporary. Change becomes credible when the old behaviour begins to carry a consequence. When a senior leader bypasses the agreed process, someone addresses it. When a legacy meeting no longer serves the strategy, it is removed. When an old measure contradicts the new direction, it is replaced.

The future cannot become normal while the past remains safer. Transformation requires addition, but it also requires subtraction. Without subtraction, change becomes more work rather than a different way of working.

Judge Adoption by Behaviour Under Pressure

Attendance at workshops is not adoption. Neither are positive survey responses, completed training modules or employees using the new vocabulary. The real test arrives when pressure returns.

• When a deadline is threatened, do leaders use the new decision process or take control themselves?
• When results fall, do they preserve collaboration or retreat into functional protection?
• When a customer problem crosses several departments, does ownership remain shared or does each function defend its own target?

Behaviour under pressure reveals which operating model the organisation actually trusts. If leadership abandons the transformation whenever the situation becomes difficult, employees will do the same.

They are not failing to adopt the change. They are following the example set at the top.

Give People a Reason to Believe This Time

Employees do not need leaders to guarantee that every transformation will succeed. They know that markets change, plans evolve and some decisions will prove wrong. They need something more realistic: evidence that leadership will remain present when the work becomes difficult. That means fewer launches and more completion. Fewer slogans and more resolved contradictions. Less pressure to display enthusiasm and more space to raise legitimate concerns.

The next transformation will not earn trust because its presentation is more persuasive. It will earn trust when employees see that leadership has remembered what happened last time and changed its own behaviour accordingly.

Resistance is sometimes fear. Sometimes it is self-interest. But often, resistance is the organisation remembering on behalf of leaders who would prefer it forgot.