There is a particular kind of exhaustion that settles into NHS organisations after a failed digital transformation. It is not the exhaustion of having worked hard. It is the exhaustion of having believed — and been let down. Of having attended the workshops, completed the training, adapted the workflows, and then watched the system get quietly decommissioned eighteen months later because the business case no longer stacked up, or the supplier couldn't deliver, or the board lost appetite.
That exhaustion is not soft. It has a direct and measurable effect on the next programme that arrives. The goodwill that transformation requires — from clinicians, from managers, from the patients whose care depends on the outcome — is a finite resource. Every failed programme spends some of it. The NHS has been spending it for a long time.
This is the context in which digital leaders are currently being asked to deploy AI diagnostics, replace EPR systems, and digitise care pathways that have been running on paper and institutional memory for decades. The technology is not the hard part. The hard part is asking people to believe again.
Governance as reassurance
The standard account of programme governance focuses on control — over scope, budget, risk, and delivery. That account is not wrong, but it is incomplete. Governance is also the primary mechanism by which an organisation communicates to its staff, its patients, and its leadership that it knows what it is doing.
A benefits realisation framework is not just a financial instrument. It is a promise: we will tell you what this programme is supposed to achieve, and we will tell you honestly whether it has. A demand management process is not just a prioritisation tool. It is a signal: your needs have been heard, assessed, and placed in an order that we can explain and defend. A show-back cost model is not just an accounting exercise. It is an act of transparency in an environment where digital investment has historically disappeared into a black box.
When governance works, it produces confidence. And confidence is what allows people to invest — emotionally, practically, professionally — in the outcome.
Confidence that the programme is being run by people who understand what they are doing. Confidence that problems will surface early rather than be managed upward too late. Confidence that the organisation's commitment to this change is genuine and sustained.
The checklist and the consultation
Researchers at Beth Israel Deaconess Medical Center described a simple change to their patient intake process: two questions added to the top of every form. How would you like to be addressed? And what is your main concern for this visit?
The first question is a gesture of respect. The second is an act of listening that reorients the entire consultation — away from what the clinician assumes the patient needs, toward what the patient actually came to say.
The surgical safety checklist offers a parallel. As a governance tool it is unambiguous — a structured process designed to eliminate preventable error. Adrienne Boissy, then Chief Patient Experience Officer at the Cleveland Clinic, suggested adding a single item: family updated. One line. No additional cost. But its presence changes what the checklist communicates to everyone in that operating theatre about what the organisation values.
Good digital governance works the same way. The structures we build around programmes — the reporting cycles, the risk registers, the stakeholder engagement frameworks — communicate something about how the organisation regards the people those programmes are supposed to serve. Governance designed with empathy asks, before it designs: what are people afraid of losing? What would make them feel safe enough to engage?
Asking before designing
During my time at Guy's and St Thomas' NHS Foundation Trust, I engaged stakeholders across 26 clinical directorates individually before digital investment decisions were made for their areas. The purpose was not to conduct a survey or generate a consultation report. It was to understand what each directorate actually needed — not what we assumed they needed — and to surface that understanding early enough for it to shape the programme rather than complicate it later.
That process was governance. It was also listening. The distinction between the two is less clear than it is usually presented.
The Health Foundation has found that 76% of NHS staff support the use of AI in patient care. The same research found that 65% worry it will make them feel more distant from patients. That gap — between supporting something in principle and fearing what it will do in practice — is where transformation programmes succeed or fail. It is not a communications problem. It is not resolved by a better engagement strategy or a more compelling slide deck.
It is resolved by building the structures that demonstrate, through action rather than assertion, that the organisation understands what its staff are afraid of and has designed the programme with that fear in mind. A phased implementation plan that protects clinical time during go-live. A benefits framework that includes staff experience metrics alongside efficiency gains. A governance process that gives clinical leads a genuine mechanism to raise concerns before decisions are made, not after.
These are not soft interventions. They are the difference between a programme that is technically delivered and one that is actually adopted.
Transformation with a purpose
The NHS is not short of digital ambition. The 10-Year Health Plan commits significant investment to digitising care, and the technology to support that ambition exists and is improving rapidly. What the NHS is short of is trust — in the organisations running these programmes, in the staying power of the commitment behind them, and in the proposition that this time will be different.
Rebuilding that trust is a governance problem. It requires programme leaders who understand that the structures they build are not just management tools — they are acts of communication with the people whose working lives and care experiences depend on the outcome.
Empathy in digital transformation is not a value to be stated in a programme vision document. It is a design principle to be embedded in how governance works, how engagement is structured, and how success is defined and measured. It starts not with the technology, but with the question the Beth Israel team put at the top of every patient form: what is your main concern?
Ask that question early enough, and design the answer into the programme, and you will have built something more durable than a system. You will have built the conditions in which people are willing to believe.