Embedding healthcare transformation: why improvements fade and how to make them last

Ask almost anyone who has worked in the NHS for a decade and they can name an improvement that worked. Then ask whether it is still working. The honest answer is often "for a while". The project closed, the programme manager moved on, the weekly meeting stopped, and within a year the service had drifted back to something close to where it started.

This is not a failure of effort or of good intentions. It is a predictable consequence of treating transformation as a project with an end date, rather than as a change to how a service runs. Embedding is the work that turns one into the other.

Why improvements fade

Improvements fade for structural reasons, not personal ones. A few show up repeatedly:

• The change depended on project resource. The analysis, the chasing and the coordination were done by people who were only ever temporary.
• Ownership was never transferred. Everyone knew who ran the project; nobody was clear who owned the new way of working once it finished.
• Measurement stopped. Once the final report was written, the indicators that showed the improvement were no longer looked at, so drift went unnoticed.
• The old system was still there. Policies, templates, forms and incentives designed for the previous way of working quietly pulled behaviour back.
• Capability stayed with the outsiders. Local teams were trained to use the new process but not to adapt it when conditions changed.

What embedding actually requires

In our DRIVE approach, Embed is a distinct stage with its own work. It is not a closing meeting. We focus on four things.

Ownership

A named person or role owns the new way of working as part of their substantive job, with the authority to maintain it. In rota work this is often a departmental rota lead working alongside the rota team, not a project manager.

Governance

A regular forum where the right people look at the right indicators and make decisions. The forum should already exist if possible. Adding a standing item to a divisional meeting is more durable than creating a new committee that will be the first thing cancelled when pressure returns.

Capability

Local teams need to be able to run and adapt the new system without external help: understanding why it was designed as it was, not just how to operate it. This is the difference between a department that can adjust its rota template when a new service opens and one that waits for the consultants to come back.

Ongoing measurement

A small set of indicators, visible to the people who own the change, reviewed routinely. The purpose is early warning. Drift is cheap to correct when it is spotted in month two and expensive when it is discovered in month fourteen.

Signals that change has embedded

• The improvement is sustained month on month, not just in the launch period.
• The people operating the system can explain why it works and have adapted it at least once themselves.
• Indicators are reviewed in a routine forum without anyone from the original project present.
• New starters are inducted into the new way of working as "how we do things here".

At Newham University Hospital, locum reductions were sustained every month across the six-month comparison period, ranging from 57% to 80%. That consistency matters more than any single month’s figure. It reflected a redesigned rota and workforce-planning process that the department owned, supported by a platform and training that were embedded alongside the new processes rather than bolted on afterwards.

Plan for embedding from the start

The most reliable way to embed change is to design for it at the diagnostic stage. Who will own this? Where will it be governed? What will people need to be able to do? What will we measure, and who will look at it? If those questions have answers before implementation begins, the end of the project is a handover rather than a cliff edge.