26 February 2026 · 12 min read · Arviteni
Care workers are not resistant to technology. They are under-supported. This guide explains what a software champions programme is, how to set one up in a care organisation, and why peer-led support consistently outperforms centralised IT training for frontline care staff.
There is a persistent narrative in care that frontline workers do not like technology. That they are resistant to change. That digital tools will always be a hard sell to a workforce that "just wants to get on with the caring."
It is wrong.
Care workers are not resistant to technology. They are under-supported. There is a significant difference between someone who refuses to use a system and someone who tried to use it, got stuck, had nobody to ask, and went back to the paper form because they had a medication round in ten minutes.
The care organisations where adoption has genuinely succeeded share a common pattern. Not the biggest IT budget or the fanciest training videos, but the right support structure around their people. The most effective version we have seen is a software champions programme.
Technology adoption in care fails for predictable, structural reasons. The technology itself is rarely the problem. The gap is between the system being available and the workforce being confident enough to use it properly.
You cannot close a care home for a day so everyone can attend a training session. Staff work shifts, weekends, nights. A session on Tuesday at 2pm will miss half the workforce. Even mandatory sessions achieve incomplete attendance because someone always needs to be providing care.
Those who miss training are expected to catch up from colleagues, written guides, or trial and error. In practice, many never do.
A care group with 500 staff might have three or four people in IT, based at a head office 100 miles from some of their homes. When a care worker cannot figure out how to complete a daily record on their tablet, the options are limited: submit a support ticket and wait, or ask a colleague who may not know either.
For time-pressured care staff, the path of least resistance is reverting to what they already know. Paper forms, a workaround in Excel, or simply not completing the digital task at all. It is not resistance. It is pragmatism.
Standard IT training covers features and functions: "here is how you navigate the menu, here is where you find reports." It rarely covers how those features fit into the specific workflow of a care worker doing a medication round or a registered manager preparing for a CQC inspection.
A care worker needs to know how to document an observation at 3am, how to record a refused medication correctly, and what to do when the system shows an error during a handover. Generic training does not answer those questions.
The most common rollout pattern: select a system centrally, configure it, run a training session, go live, move on to the next project. There is rarely a sustained support plan for the weeks and months after launch, which is precisely when the real questions emerge.
Day one questions are simple: where do I log in, what is my password. Week three questions are harder: why did my record not save, what do I do when the system does not accommodate the way we actually work here. Without ongoing support, those questions go unanswered or generate frustration that hardens into permanent avoidance.
This pattern is not unique to any one system. We see it with care planning platforms, rota software, HR systems, and even Microsoft 365. The technology works. The support model does not.
A software champions programme places a peer advocate for technology in every region, team, or location within a care organisation. Champions are not IT deputies. They are not expected to fix servers or handle security incidents. They are care staff first, who take on an additional role as the go-to person for technology questions within their local team.
The key distinction is that champions are peers. A care coordinator helping another care coordinator, a senior carer showing a colleague. They understand the pressures and the daily reality because they live it. When a champion shows someone how to complete a task, they are doing it from the perspective of someone who uses the same system in the same context, not someone from head office who has never worked a night shift.
We established a software champions programme for a care group delivering residential, supported living, and domiciliary care across multiple regions. Adoption improved, support tickets for basic queries dropped significantly, rollouts went smoother, and for the first time, the IT team had a reliable feedback loop from frontline staff about what was actually working and what was not.
The best champions are usually already doing the job informally. Every care organisation has them: the care coordinator who shows new starters how to use the rota system, the senior carer who happily walks colleagues through the reporting tools, the registered manager who always seems to fix things before anyone contacts IT.
They are patient. A good champion never makes someone feel foolish for asking a question. They understand that the colleague who is anxious about using a tablet may be brilliant at delivering compassionate, complex care.
They are curious, not necessarily technical. Champions do not need to be IT experts. Willingness to explore and try a few things before giving up is more valuable than existing knowledge.
They are respected by their team. A champion's effectiveness depends on their relationships. Staff will ask for help from someone they trust. A technically capable person who is not well liked will not succeed in the role.
They want to do it. Champions who are voluntold into the role will treat it as a burden. Those who genuinely want to help their colleagues will do it naturally and willingly.
Ask regional managers and registered managers a simple question: when someone in your team has a problem with technology, who do they ask? The answer usually points you to your champions. In some teams, the answer is "nobody," which tells you something important about the support gap.
Aim for at least one champion per site. In larger homes with 50 or more staff, you may need two or three for shift coverage. Domiciliary care teams may need a champion per locality rather than per team.
Standard user training teaches how to use a system. Champion training teaches how to support others in using it. That includes understanding why features work the way they do, recognising common mistakes, knowing when to escalate to IT, and learning techniques for helping colleagues who find technology intimidating.
Champion training should be practical and workflow-focused. Teach them to walk a colleague through a shift handover, a medication refusal entry, or the report their registered manager needs for a CQC visit.
Champions operating in isolation will burn out or drift away. Create a community: a monthly video call, a dedicated Teams channel, or both. Champions share problems and solutions. The IT team communicates upcoming changes through the champion network before they reach the wider organisation. Champions feel connected to something bigger than their local team.
This community also becomes the organisation's most reliable source of frontline feedback. When a champion reports that care workers in three different regions are all using the same workaround, that is actionable intelligence for the IT team. Several insights from champions we have worked with have led directly to configuration changes that improved systems for everyone.
This is where the programme pays for itself most visibly. Before a new system goes live, champions get early access and additional training. They familiarise themselves with the changes and identify friction points specific to their team's workflow.
On launch day, every care worker has someone nearby who has already used the new system. Compare this to the traditional approach: an email, a webinar half the workforce cannot attend, and hope. The difference in adoption is substantial.
This applies even to straightforward changes. When an organisation standardises hardware by role, champions help colleagues set up new devices, transfer workflows, and adjust. The technology may be better, but change still needs support.
Champions are doing something valuable. Recognise it. This does not have to mean financial incentives, though a development opportunity is welcome. At minimum: acknowledge champions in team meetings, ensure their line managers support the role, include it in appraisals, and give champions a voice in technology decisions.
The worst thing an organisation can do is appoint champions and forget about them. Without visible support from leadership, the programme will quietly fade.
When a champions programme is running well, the effects are visible across the organisation.
Adoption rates improve. Care workers who avoided the digital care planning system start using it because a colleague sat with them and showed them, patiently, in the context of their actual work.
Support tickets drop. The simple questions filling the IT helpdesk queue get resolved locally, in real time, often faster than it would take to write the ticket. The IT team is freed up for complex technical work that genuinely requires their expertise.
Feedback flows back to IT. Champions provide something richer than support tickets: observational feedback about what care workers actually do with the tools, where they struggle, and what they wish worked differently. This improves system configuration and informs better purchasing decisions.
Rollouts go smoother. The cycle of launch, confusion, and gradual abandonment is replaced by a supported transition where care workers feel guided rather than left to figure things out alone.
Staff confidence grows. When care workers have positive experiences with technology, supported by someone they trust, they become more willing to engage with the next system, the next update. Technology stops feeling like something that is done to them and starts feeling like something they can use effectively.
Champions are care staff with an additional role, not full-time IT support. If a champion is spending more time on technology support than on their primary role, the balance is wrong. Set clear expectations and ensure champions know when to escalate.
If champions are expected to support colleagues during rollouts but are not given protected time to do so, the programme will fail. Even a few hours per month, factored into rotas, makes a significant difference.
Without visible support from directors, champions are enthusiastic individuals with no authority. When a registered manager dismisses the role as "not a priority" or refuses to release a champion for training, the programme loses credibility.
Champions leave, change roles, or lose momentum. The community needs ongoing facilitation. Treat the programme as a permanent part of your technology support structure, not a project with an end date.
Appointing someone because they are "good with computers" rather than because they are patient, approachable, and respected will not produce good results. Technical skill is easier to develop than interpersonal skill. Prioritise the human qualities.
There is a tendency to treat technology adoption as an IT metric. Logins, usage rates, ticket volumes. Those numbers matter, but they obscure the real point.
When a care worker cannot use the digital care planning system, they either skip the observation or record it on paper and hope someone enters it later. Both create gaps in the care record. The next carer on shift may not know about a change in condition, a refused meal, or a concerning behaviour. That is not an IT problem. That is a care quality problem.
When a registered manager cannot generate reports from the system, they spend hours compiling data manually instead of being on the floor with residents. When nobody can use the HR platform properly, recruitment slows, onboarding falters, and the workforce suffers.
Technology adoption in care is not about getting people to use computers. It is about ensuring that the tools designed to support better care actually deliver on that promise. That requires more than good software and a training manual. It requires human support, from people who understand the work, delivered in a way that meets care workers where they are.
A champions programme is not the only thing you need. You still need well-configured systems, reliable infrastructure, consistent equipment, and an IT team that understands care. But without peer-led support at the frontline, everything else you invest in technology will underperform.
Your care workers are not the problem. Your support model is. Fix that, and adoption follows.
If you are considering a software champions programme or need help improving technology adoption across your care organisation, our technology consulting service works with care providers to design support structures that make technology work for frontline staff. Not in theory. In practice.