Danny Weston, client partner at NEC Digital Studio, argues that NHS technology fails when it forgets how care is actually experienced.
Talk of digital transformation in the NHS often becomes a numbers game. Waiting lists are falling. Targets are being met. Ministers talk about the need to move faster with technology to improve productivity and patient flow. Health secretary Wes Streeting has cautioned that the real risk is not moving too fast, but moving too slowly with NHS technology, emphasising that running 21st-Century services on analogue systems wastes both time and human potential.
Yet when we look at what actually works for patients and staff, speed is only part of the picture. The deeper issue is the disconnect between how we think systems should work and how people actually experience them. Across the health service, there are many teams doing thoughtful work to improve this, often under intense pressure. What makes progress difficult is the complexity of trying to redesign systems while they are still carrying heavy demand.
In too many parts of the service, digital initiatives are launched with fanfare and strategic intent. They promise seamless pathways and joined-up care. But when patients engage with these systems, they often encounter frustration, confusion or barriers that make care feel disjointed rather than connected. Staff face similar frustration. Basic clinical systems fail to talk to each other. Colleagues describe scenarios where they must open multiple records screens just to piece together a patient’s journey. These are not isolated anecdotes. They reflect systemic friction that technology alone has not resolved.
Visual maps
Work in urgent and emergency care offers a useful illustration. NHS England has begun to build visual maps that show how IT tools, databases and pathways interact across urgent care settings. These maps, created through inclusive system-wide workshops, reveal bottlenecks not just in clinical flow but in information flow. Visualising these interactions helps leaders understand where digital tools support patient journeys and where they inadvertently create blind spots. Importantly, exercises like this do not always require major investment. Sometimes they begin with something as simple as paper mapping sessions that bring together frontline staff and representative users. Those relatively low-cost exercises can generate valuable insight before expensive technology decisions are made.
These approaches focus less on technology alone and more on seeing the whole picture. This is the essence of systems thinking, and it matters because the human experience, that of the patient and clinician alike, is where the success or failure of digital change becomes real.
When we neglect lived experience, we risk designing services that satisfy performance metrics but fall short in practice. For example, a centralised triage system may streamline access on paper, yet if it routes a parent with a sick child through eight-layered menus before they reach clinical help, it generates anxiety rather than reassurance. Human experience extends beyond digital confidence. It includes people managing mobility challenges, language barriers, anxiety, unstable housing, caring responsibilities or simply the practical difficulty of navigating services while looking after young children. And there will always be some people who will never fully move to digital channels. Understanding their needs is part of making transformation work and strengthens the design of services for everyone.
This does not diminish the importance of platforms and technology. They remain essential, but they do not operate independently of organisational reality. Services only feel coherent when they align with how care is actually delivered and received. Systems thinking invites leaders to zoom out and see the broader landscape while also zooming in on individual experience. This duality helps avoid the trap of building elegant architecture on flawed foundations. It surfaces critical questions about equity, access and usability that purely structural thinking overlooks. Mapping systems conceptually before implementation also helps teams test assumptions, explore trade-offs and refine design choices early, when change is still relatively inexpensive. By the time technology is commissioned and deployed, those same changes become significantly harder and more costly.
For instance, if we discover in co-design sessions that patients living with multiple long-term conditions repeatedly re-register with different services because their information is not shared, that insight challenges assumptions about interoperability. It points to specific changes required not just in data standards but in how front-end systems present options to users.
Reframing priorities
Leaders can shift from operational compliance to meaningful transformation by reframing priorities. They can redefine success so it reflects measurable improvements in how people navigate and feel supported by the system. They can involve service users and clinicians early, treating them as partners in shaping design and evaluation.
Embracing systems thinking grounded in human experience does not require waiting for perfect conditions. It begins with listening attentively. It begins with acknowledging complexity rather than simplifying it away. It begins with framing technology as an enabler of experience, not an organiser of it.
Integrating lived experience into digital design is essential to building services that scale safely and sustainably. When technology is rooted in how people actually live and work, it becomes a platform for connection and care rather than an obstacle to be navigated.
We cannot afford to think of digital transformation as simply a matter of pace. The pace question invites a race. What we need is a journey: one that recognises people as the heart of the system and builds technology in service of that reality.
