What Is Change Management? And What Does Organisational Resilience Add?

I’ve spent a fair amount of time telling people “change management is dead.” It is a magnificent sentence for a slide: three words, instant tension, and every change practitioner in the room suddenly has a reason to stay awake. Then I tried to prove it and discovered that the corpse was inconveniently still breathing.

The deeper I went into the evidence while building Antistable, the harder my argument became to defend. Modern change management already deals with continuous change, organisational capability, adoption and the very human problem of getting people to work differently. I had created a tidy opponent because it made the resilience argument easier to explain.

What I was actually interested in was something else: successfully managing a transformation tells us that an organisation can deliver that transformation. It does not automatically tell us how capable the organisation will be when circumstances move again. And again.

What is change management?

Prosci is one of the best-known organisations in the change-management field. Founded in 1994, it has spent more than 25 years researching the people side of organisational change and is best known for tools including the ADKAR model. Prosci describes change management as a structured approach to enabling the people side of change and, at enterprise level, treats it as an organisational capability rather than something that only appears when a project starts.

Just because leadership approves a new operating model on Monday, it does not mean everyone turns up on Tuesday understanding why it exists, what has changed in their role and how they are supposed to behave differently. Humans remain irritatingly resistant to PowerPoint osmosis.

Chip and Dan Heath’s Switch has been useful in my own work for exactly that reason. Their Rider, Elephant and Path model separates rational clarity, emotional motivation and the environment surrounding behaviour. You can explain the new direction perfectly and still fail because people do not want to move, cannot move, or the system keeps rewarding the behaviour you are trying to remove.

Change management has an important job because deciding that something should change and getting an organisation to actually change are different activities. My original criticism underestimated how far the discipline had developed; the idea that change management handles neat little projects while resilience deals with the messy real world does not hold up particularly well.

The question I should have been asking was what successful change management does not tell us.

What happens after the transformation succeeds?

Imagine a business completes a difficult transformation. The technology works, people are using it, processes have changed and the expected benefits are starting to appear. Everyone involved is finally permitted to stop saying “transformation journey” for five minutes.

Six months later, a major assumption turns out to be wrong. A competitor changes the economics of the category. Customer behaviour shifts. Or the transformation itself creates pressure in a part of the organisation nobody was watching.

Now I want to know how quickly the business will notice, whether somebody can raise the problem without it being polished into something more comfortable on its journey upwards, and whether there is enough capacity left to respond. I want to know whether leaders can abandon the original plan when the evidence says it no longer fits, and whether the organisation can turn the next decision into action without quietly dumping the pressure somewhere else.

Landing the original transformation tells us something important about the organisation. It just doesn’t answer all of those questions.

Organisational resilience is more than bouncing back

The International Organization for Standardization (ISO) is the global standards body behind thousands of internationally recognised standards used across industries. In 2017 it published ISO 22316 specifically on organisational resilience. Rather than treating resilience simply as recovery after disruption, the standard focuses on an organisation’s ability to absorb and adapt as its environment changes while continuing to achieve its objectives. Its guidance also covers changing context, anticipation, risk, opportunity, culture and leadership. The 2017 edition remains current, although ISO now has a second edition in final approval that will replace it.

Academic research reaches a similar place. Stephanie Duchek, an organisational-resilience researcher at Technische Universität Dresden, developed a capability-based model that has become an influential academic reference in the field. Her model looks at resilience across three phases: anticipation, coping and adaptation – what an organisation can do before pressure arrives, while dealing with it, and once it has learned something from the experience.

Sometimes recovery is exactly what is required. Sometimes returning everything to the way it worked before would be the organisational equivalent of carefully rebuilding the pothole. There is something slightly odd about celebrating a business for returning perfectly to the condition that got it into trouble in the first place. That is less resilience and more organisational muscle memory.

If you are looking at change management vs organisational resilience, the mistake is assuming you have to choose between them. I now separate their jobs like this: change management helps organisations make intended change work, while organisational resilience asks whether the organisation remains capable as the conditions around it keep changing.

There is plenty of overlap, as there should be. A business that repeatedly fails to implement necessary change would be difficult to describe as resilient, and strong change-management capability can contribute to organisational resilience. Resilience keeps asking questions after the change has landed: can the business see pressure developing, make sense of it early enough to create options, use the capability inside its people and respond without exhausting the organisation in the process?

The employee is an easy place to put the problem

The difference becomes practical when change starts struggling. Organisations have a remarkable ability to discover that the problem is the employee: they are resistant, they lack the right mindset, they need to embrace uncertainty. There may be a workshop, almost certainly accompanied by a stock photograph of someone jumping between rocks.

“Resistance to change” can become an impressively efficient diagnosis. It explains everything while requiring almost no investigation of the people doing the diagnosing.

Sometimes people genuinely do resist necessary change. Individual responsibility does not vanish because systems exist. Research into resistance to organisational change, however, also points to trust in management, leadership, participation, communication and perceptions of justice alongside individual factors such as cognitive flexibility.

The broader resilience research I’ve done reached a similar conclusion. Psychological safety, communication, agency, flexibility, support and underlying capacity all influence whether people can respond effectively under pressure. Resilience starts looking less like a personality trait and more like the result of people interacting with the system around them.

Before deciding that people are resistant to change, I now want to know whether the organisation is making adaptation unnecessarily difficult. The employee may need to change. The business may need to change. Frequently both do. Finding out which part of the system is creating the friction beats prescribing another dose of resilience to whoever happens to be standing nearest the problem.

Anticipate, Design and Implement

The framework I use to examine that problem did not originate with me. I first encountered Anticipate, Design and Implement through my studies with the Global Reinvention Academy and have subsequently adapted the framework from the reinvention context into the business system through Antistable.

In the Antistable application, Anticipate means noticing what may be changing early enough to create options before pressure becomes crisis. Design means making sense of that change and shaping a purposeful response that fits the organisation, its people and its environment. Implement means turning the response into coordinated action and sustaining it long enough to create the intended result.

The adaptation to the business system is where the work gets interesting. An individual can be exceptional at spotting what is coming while working in an organisation where nobody wants to hear it. Someone else can design a strong response but have no authority or agency to influence the decision. A team can be brilliant at implementation and still grind to a halt after being handed seventeen competing priorities and apparently being told that sleep is a limiting belief.

Antistable therefore looks at both sides of the equation: the capability people bring to changing conditions and the organisational environment that allows – or prevents – that capability from being used. Organisational resilience cannot simply mean asking increasingly resilient people to compensate for an increasingly difficult system.

Three questions before adding another change

Before adding another major initiative, I would want to know three things:

1. Can we Anticipate early enough to create options? Look at how information enters the organisation, how quickly uncomfortable signals reach decision-makers and which problems repeatedly become visible only once they are urgent.
2. Can we Design a different response when reality changes? Look at whether people have enough agency and psychological safety to challenge the existing plan, whether assumptions can actually be revised and whether there is enough room to choose rather than simply react harder.
3. Can we Implement without breaking something else? Look at real capacity, competing priorities and coordination across the organisation. A response that fixes one problem by quietly transferring the strain into another department may have moved the problem rather than solved it.

These questions do not replace good change management. They widen the view around the change and ask whether the system carrying it remains capable of carrying what comes next.

Change management isn’t dead. My slide was.

If you are implementing a new technology platform, restructuring a business or asking hundreds of people to work differently, good change management matters. People need clarity, support and an environment that allows new behaviour to stick. Someone still has to worry about adoption rather than declaring victory because the software went live.

Organisational resilience keeps the lens open after that. It asks whether the business can still notice what is shifting, whether people still have capacity, whether uncomfortable information can surface and whether the organisation can revise its response without losing the ability to operate while it does so.

So I am retiring “change management is dead.” I will miss it; it was an extremely efficient slide. The argument I trust more is that successfully managing the change in front of you and building an organisation capable of dealing with the change you cannot yet see are related, but different, jobs.

That is the second problem I am adapting Anticipate, Design and Implement to help organisations understand through Antistable.