A well-designed change can still fail if the organisation around it is left untouched.

The case for change may be compelling, the intended outcome clear and the delivery plan credible. But the work still depends on existing structures, decisions, policies, priorities and relationships.

If those conditions do not move, the programme is forced to compensate for them.

Teams are given accountability without authority. New services are introduced into operating models that were never redesigned to support them. Governance continues to reinforce previous priorities. Delivery becomes dependent on escalation, personal relationships and repeated exceptions.

Progress may continue, but sustainability declines. Change is not an island. It is part of an organisational system.

When the change moves but the organisation does not

Transformation programmes are usually designed around a future state. They describe new services, processes, technologies, responsibilities or ways of working, then create a route from the current position to that intended future.

The difficulty is that the wider organisation may continue to operate according to the current state.

Existing governance forums still expect the same information. Budget arrangements reinforce established boundaries. Teams remain accountable for local priorities. Decision rights are unclear. Policy and assurance requirements reflect earlier assumptions.

The programme then has to work around the organisation rather than through it.

Additional coordination is introduced to bridge gaps between teams. Temporary forums are created to secure decisions. Leaders rely on personal relationships to resolve issues. Exceptions become routine, and progress depends increasingly on the knowledge and persistence of particular individuals.

Delivery may continue, but the organisation has not yet absorbed the change.

When the programme starts compensating for the system

Programmes often absorb organisational problems because delivery still has to move. That response can be understandable in the short term, but it creates a hidden dependency.

A temporary decision forum becomes the only place where cross-cutting issues can be resolved. A programme team retains operational knowledge because no sustainable home has been created. Senior sponsorship substitutes for clear decision rights. Repeated exceptions allow work to continue without changing the policy or control that created the barrier.

The programme appears resilient, but much of that resilience sits in workarounds rather than in the organisation itself.

If progress depends on continually bypassing normal arrangements, those arrangements have not yet changed enough to sustain the outcome.

The warning signs

The pattern is often visible before delivery fails. Warning signs include:

• the same decisions returning to several forums without resolution;
• accountability resting with people who do not control the resources, policy or dependencies involved;
• temporary governance continuing because the permanent structure cannot make the required decisions;
• exceptions becoming normal practice rather than prompting a change to policy or controls;
• assurance findings recurring without influencing investment, prioritisation or design;
• progress depending on a small number of people who know how to navigate the system; and
• new processes being followed only while the programme provides active intervention.

Viewed separately, each issue may appear manageable. Viewed together, they show that the system surrounding the transformation is not aligned.

Design the conditions as well as the change

Transformation design must extend beyond the intervention itself. It should define what must be true around the work for the intended outcome to become normal organisational practice.

How decisions will be made

Be clear which decisions sit within the programme, which belong to the wider organisation and how cross-cutting issues will be resolved. Decision-making needs enough pace to maintain progress while preserving appropriate accountability, evidence and challenge.

Where accountability sits

Naming someone as accountable does not give them the authority, capacity or control needed to deliver the outcome. Leaders need to identify the decisions, resources and cross-organisational dependencies behind that accountability, then resolve any gap between responsibility and the practical ability to act.

How the operating model will sustain the outcome

A future service or capability needs a durable organisational home. Roles, resources, capabilities, processes and interfaces must be designed deliberately rather than assuming the programme structure can simply disappear after implementation.

Which policies and controls must change

New ways of working often expose outdated rules, overlapping requirements or controls designed for a different context. Policy and assurance need to evolve alongside the change so that responsible delivery becomes easier, not dependent on repeated exceptions.

How evidence will change delivery

Transformation generates evidence. Assumptions are tested, risks develop and operational constraints become clearer. Assurance and learning arrangements should bring that evidence into decisions, so adaptation is treated as responsible management rather than failure to follow the original plan.

Readiness is more than willingness

Organisations often describe themselves as ready for change because leaders support the ambition or colleagues recognise the need for something different.

That support matters, but readiness is more practical than willingness.

An organisation is ready when it can make the required decisions, absorb new responsibilities, provide appropriate capacity, manage risk and sustain the resulting way of working.

People can be fully committed to the outcome and still be working in a system that makes the change unnecessarily difficult.

Completion is not integration

A programme can implement an output. Sustainable transformation requires the organisation to adopt and maintain the resulting change.

A new process may have launched, but it is not sustainable if teams need constant intervention to follow it. A governance model may have been approved, but it is not effective if decisions continue to be made elsewhere. A capability may have transferred into operations, but it is not embedded if the necessary skills, capacity and ownership are absent.

The practical test is whether the organisation can now operate differently without relying on the programme that created the change.

Is the organisation changing with the programme?

Test whether the organisation can sustain the new way of working without continued dependence on temporary forums, repeated exceptions or individual persistence.

If it cannot, the programme may have delivered an output, but the change is not yet embedded.