Change Management Is Finally Being Taken Seriously. But Many Organisations Are Still Bringing It In Too Late.

There is something encouraging happening across transformation right now: more organisations are investing in dedicated Change Management capability. 

Change Managers are being recruited into programmes that, in previous years, might have relied almost entirely on project delivery, communications and training. Heads of Change are becoming more visible. Transformation functions are increasingly recognising that implementation alone does not create adoption, and that successful delivery depends on what happens beyond the technical solution.

That is progress, and it should be recognised as such.

However, I also think many organisations are still missing an important part of the opportunity. They are taking Change Management more seriously, but they are continuing to bring it into the transformation lifecycle too late.

In many programmes, the strategic direction has already been agreed, the solution has been designed, budgets have been committed, timelines have been set and governance is already in motion before meaningful Change involvement begins. At that point, the Change Manager is often asked to focus on stakeholder engagement, communications, training and, ultimately, adoption.

Those activities matter, but if this is where Change Management begins, then much of its strategic value has already been lost.

Adoption should not be the starting point

Adoption is one of the clearest indicators of whether a transformation has actually landed, but it should not be treated as the point at which Change Management becomes relevant.

By the time an organisation is asking how to encourage adoption, many of the most consequential decisions may already have been made.

The operating model may already have been defined. Roles may have shifted. Technology may have been selected. Processes may already have been redesigned. Implementation dates may have been committed to senior stakeholders. The benefits case may already assume that people will behave differently once the new solution is available.

If the organisational and behavioural implications of those decisions have not been considered early enough, the Change function is placed in a reactive position. It is left trying to mitigate risks that could have been identified during design, rather than helping to shape the conditions that make successful implementation more likely.

This is the distinction between using Change Management as an adoption service and using Change leadership as a strategic capability.

The strongest value is often created upstream

A strong Change leader should be involved while the transformation is still being shaped, because the quality of early decisions has a direct impact on what becomes possible later.

At portfolio and programme level, Change insight can help leaders understand whether multiple initiatives are converging on the same populations, whether managers have the capacity to absorb another significant change, whether there are unresolved behavioural dependencies within the business case, and whether the organisation is genuinely ready for the level of disruption being proposed.

These are not peripheral questions.

They are fundamental questions about delivery risk, organisational capacity and value realisation.

A transformation may be technically sound while still being poorly sequenced. A programme may be strategically important while landing at the wrong time for the teams expected to absorb it. A new process may be well designed while relying on behaviours that have never been built. A strong business case may still fail if the people required to deliver its benefits are not sufficiently prepared, supported or aligned.

That is why Change leadership should be represented earlier in the transformation conversation.

People centred does not mean less strategic

Part of the problem is that organisations often continue to separate the “people side” of transformation from the more traditionally strategic elements of the work.

Technology is viewed as technical. Finance is viewed as commercial. Operating model decisions are viewed as structural. Portfolio management is viewed as strategic. Change Management can then be positioned as the function responsible for helping people accept or understand what has already been decided.

I think that framing is increasingly outdated.

People centred transformation is not about making difficult decisions feel more comfortable. It is about understanding how organisational systems actually respond when those decisions are introduced.

A technology implementation has limited value if employees build workarounds around it.

A redesigned operating model has limited value if decision rights remain unclear in practice.

A new process has limited value if managers continue to reward the old behaviour.

A portfolio of individually well managed projects can still create enterprise wide failure if too many changes land on the same teams at once.

Human behaviour is therefore not an adjacent consideration. It is one of the mechanisms through which strategy becomes performance.

The Head of Change needs a portfolio view

This is also why the role of senior Change leadership needs to be broader than managing a team of Change Managers or allocating resource to projects.

A mature Head of Change should have visibility across the transformation portfolio and should be able to see where different initiatives are competing for the same organisational attention.

That means understanding where major changes are landing, which populations are repeatedly affected, where management capacity is becoming constrained, where leadership sponsorship is weak, and where the organisation may be moving faster than its ability to absorb change.

It also means having enough authority to challenge sequencing, identify cumulative change load and recommend different levels of Change support depending on the level of risk.

Not every initiative requires the same depth of intervention.

Some programmes will require embedded Change leadership. Others may need targeted support, strong manager enablement or self service capability. In some cases, the right decision may be to delay or resequence work because the organisation simply does not have the capacity to absorb it well.

That is not resistance to delivery.

It is responsible transformation governance.

AI makes this even more important

The growth of AI introduces another important dimension to this discussion because project delivery is becoming faster.

Planning can be accelerated. Analysis can be completed more quickly. Communications can be drafted in minutes. Large volumes of stakeholder feedback can be synthesised far more efficiently than before. Scenario modelling, reporting and administrative tasks can increasingly be automated.

This creates enormous potential, but it also creates a new tension.

Delivery capability can now accelerate faster than organisational readiness.

If organisations use AI primarily to compress timelines without strengthening their ability to understand and manage the human implications of change, then adoption risk may actually increase.

This is where I think tools such as Claude become particularly valuable for senior Change leaders.

AI can help analyse portfolio information, identify overlapping impacts, synthesise readiness signals, challenge assumptions within a business case, detect recurring themes in stakeholder feedback and surface areas where delivery confidence may be stronger than organisational readiness.

That does not mean AI should make the decision.

It means AI can improve the quality, breadth and speed of the analysis available to leaders who still need to exercise judgement.

For me, that is a much more strategic use of AI in Change Management than simply using it to produce communications faster.

What organisations need to do differently

Hiring more Change Managers is a positive step, but recruitment alone will not create mature Change capability.

If the organisational model remains unchanged, then the function can simply become a better resourced version of the same late stage intervention.

The more important shift is to reposition Change earlier in the transformation lifecycle.

Change leadership should have a voice in portfolio design, programme shaping, investment decisions and transformation governance, particularly where there are significant implications for organisational capacity, behavioural change or benefit realisation.

This also requires clearer operating disciplines.

Organisations need transparent Change triage, clear service offers, agreed decision rights and a stronger understanding of when different levels of Change support are appropriate.

Senior Change leaders should also have access to portfolio wide information, because it is difficult to advise on organisational readiness when every project is assessed in isolation.

The aim is not to add another approval layer.

It is to improve decision quality before expensive commitments are made.

The next stage of Change maturity

The growing demand for Change professionals is encouraging because it reflects a greater recognition that transformation cannot succeed through technical delivery alone.

The next stage of maturity, however, is not simply about hiring more Change Managers.

It is about changing where Change sits in the organisational system.

The most mature organisations will stop asking:

“When should we bring the Change Manager in?”

and begin asking:

“Where does Change insight need to influence this decision before we make it?”

That is a fundamentally different proposition.

It moves Change Management away from being primarily an adoption function and towards becoming an enterprise capability that helps leaders make better transformation decisions.

And, in my view, that is where the profession creates its greatest value.