Why aren’t staff adopting the new technology? A practical guide for NHS leaders
Staff may struggle to adopt new technology because it adds work, disrupts established routines or leaves important questions unanswered. Training can help, but improving uptake starts with understanding what makes the technology difficult to use in everyday practice.
For NHS leaders, this means looking closely at the experience behind the adoption figures.
A system can be available, staff can have completed training, and implementation can still be struggling. Before describing the problem as “resistance to change”, it is worth asking: what are people being asked to do differently, and what is getting in their way?
What does “resistance to change” actually tell you?
To begin with "resistance" isn't always an accurate explanation of people's attitudes. It is often too broad to be useful.
Someone who lacks confidence needs different support from someone who understands the system but cannot fit it into their working day. A concern about professional judgement needs a different conversation from a problem with access or reliability.
Research offers a useful way of widening the discussion. The NASSS framework, developed by Greenhalgh and colleagues, examines technology adoption across the technology itself, its users, organisational conditions and the wider context. It encourages leaders to explore how these factors interact over time. It is a framework for understanding complexity, rather than a formula for successful implementation.
A more useful starting question is: “What makes using this technology difficult in the circumstances where we expect people to use it?”
That gives you something specific to investigate.
Does the technology fit the way work actually happens?
A demonstration shows how a system is intended to work. Your team can show you what happens when the clinic is running late, a colleague is absent or information is missing.
Consider a hypothetical example: a new tool reduces the time needed to complete one task, but staff still have to enter the same information into another system. The benefit may be real, while the overall experience remains frustrating.
Ask a small group of staff to walk through a typical task, from beginning to end. Include people working different shifts and roles.
Look for:
Information being entered more than once.
Extra checks or handovers introduced by the change.
Points where staff switch back to the previous process.
Tasks that have moved to someone else without an explicit agreement.
Give each issue an owner and a next step. Otherwise, listening becomes another activity that staff contribute to without seeing a result.
Why might more training fail to improve uptake?
Training is useful when it addresses the actual difficulty.
A 2025 umbrella review covering 65 systematic reviews of digital nursing technologies identified barriers including insufficient training, increased workload and low technological confidence. Concerns about autonomy and professional roles also mattered. Leadership support and alignment with care needs were among the factors supporting implementation. Read the review.
The practical question is whether staff need further instruction, supported practice or a change to the working conditions around the technology.
Before commissioning another training session, ask:
“What can people do confidently after training, and where do they still need help?”
Then make support specific. That might mean practising a difficult scenario, arranging help during a particular shift or clarifying an unfamiliar step.
Recording attendance tells you who attended. You still need to establish whether people can use the system confidently in the situations they encounter.
What concerns are staff trying to resolve?
New technology can change how people understand their contribution and responsibilities.
An experienced professional may want to know when to trust a tool, how to challenge its output or what happens when it conflicts with their judgement. These are substantive implementation questions.
A 2026 evaluation of an AI fracture-detection implementation in Norway identified clinician trust, workflow integration and the distribution of tasks as important factors. It also highlighted concerns about deskilling. This was one implementation in a particular healthcare setting, so its findings should inform questions rather than be treated as a universal prescription. Read the study.
For your own programme, make space for questions such as:
What remains my responsibility?
Where should I take a concern about the tool?
How will changes to our roles be agreed?
What happens when the system is unavailable?
Work through these questions with the relevant clinical, technical and governance leads. Where an answer is still being developed, explain who is resolving it and when staff can expect an update.
Can people tell you when implementation is going badly?
Consider how you would respond if someone said:
“This is taking longer than our previous process.”
Would you ask them to show you? Or would the conversation quickly become an explanation of why the change is necessary?
Leaders need usable feedback, including feedback that challenges the implementation plan. A practical approach is to ask for a recent example, explore what happened and agree what should be checked.
Be clear about which aspects of the implementation staff can influence. If a decision is fixed, explain that honestly while identifying where their experience can still shape delivery.
Close the loop afterwards. A short update explaining what changed, what could not change and why is more useful than repeatedly asking for views without reporting back.
What should you do if adoption has stalled?
Start with one team and one important workflow.
Compare the intended process with what staff actually do. Speak with regular users and people who are struggling. Check whether the main difficulty concerns capability, workload, trust, unclear responsibilities or the technology itself.
Choose a manageable change and review whether it helps. Alongside usage, consider duplicated work, requests for support and staff confidence. Agree any relevant clinical safety and quality measures with the appropriate leads.
At Nicole Williams Organisational Psychology, we help organisations understand the people, leadership and cultural factors affecting change. An organisational psychology perspective can help turn a broad concern about “engagement” into clearer questions about what needs to change and who needs to be involved.
Explore the human side of NHS digital transformation
If you are introducing new technology and want to understand what helps it become part of everyday practice, join our free webinar:
Beyond the Technology: The Human Factors That Make or Break Digital Transformation in the NHS
Wednesday 25th November 2026, 13:00–14:00 (GMT)
The session brings together organisational psychology, NHS implementation experience and strategic communications to explore the human factors influencing adoption.
References:
Greenhalgh T, Wherton J, Papoutsi C, Lynch J, Hughes G, A'Court C, Hinder S, Fahy N, Procter R, Shaw S: Beyond Adoption: A New Framework for Theorizing and Evaluating Nonadoption, Abandonment, and Challenges to the Scale-Up, Spread, and Sustainability of Health and Care Technologies
Walzer S, Armbruster C, Mahler S, Farin-Glattacker E, Kunze C: Factors Influencing the Implementation and Adoption of Digital Nursing Technologies: Systematic Umbrella Review
Severinsen GH, Silsand L, Ellingsen G, Pedersen R: Implementing a Commercial AI Fracture Detection Tool in Health Care Using the Non-Adoption, Abandonment, Scale-Up, Spread, and Sustainability Framework: A Formative Evaluation Study

Nicole Williams is a Chartered Occupational Psychologist and founder of Nicole Williams Organisational Psychology, supporting organisations with workplace culture, leadership, team dynamics and organisational change.

Comments