Implementation and Adoption: Making Technology Stick

The Most Expensive Care Technology Is The One Nobody Uses

Most care technology that fails was never bad technology. It was chosen carefully, installed correctly, and everyone was trained. The project was signed off as complete.

Then six months later it’s barely being used, the team has quietly built its own workarounds, and nobody entirely trusts the data.

We work on shift with your team, days and nights, to turn a system that’s installed into one that’s genuinely part of care.

What changes at 3am

One row. Every role in the service gets one.

Changes

The escalation path, at the exact hours when there are two of you on.

Worries

Being alone with an alert and nobody to ask.

Learns by

Doing it on their own shift, in real conditions.

90 days

A new night starter can be shown the whole thing by the night senior.

The Adoption Map is where we start. It takes ninety minutes with your team and it decides more than any training session will.

Installation is not implementation

Installation is getting the technology into the building. It can happen in a day. Implementation is making it part of how care is delivered, and that takes a season.

A system isn’t implemented because it’s switched on and demonstrated. It’s implemented when the night team knows what it means for them at three in the morning. When a nurse trusts the information enough to act on it. When agency staff know what’s expected of them. When a new starter learns it properly in induction rather than picking it up as folklore from whoever’s on shift.

That’s adoption, and it’s the part almost nobody budgets for.

Spark Care was built by people who have run care homes, which is why this service exists at all. We kept watching good technology fail for reasons that had nothing to do with the technology.

From installed to everyday

Time on shift

Days and nights, watching how information really moves and where it gets lost.

Adoption Map

Role by role, what changes, what worries people, and what good looks like at ninety days.

Training that fits

Built around how your people learn, not around what's convenient to deliver.

The first ninety days

We stay through the period that decides it, when the novelty wears off.

Made to last

Induction, refreshers and internal champions, so it survives your rota.

What looks like resistance is usually information

“Our staff are resistant to technology” has become the standard explanation for a rollout that stalled. We’ve stopped accepting it at face value.

When you sit with the reluctance long enough to ask about it properly, it’s almost always one of these.

A genuine, accurate read on workload

Memory of a previous rollout that was badly handled

Worry about being monitored rather than supported

Confusion about who is responsible for responding

Low digital confidence nobody has made it safe to admit

Training that didn't reflect what this person actually does

Alerts that are too frequent, unclear or poorly configured

A process that works in theory and falls apart on a busy shift

A belief that the technology is meant to replace judgement

None of that is an obstacle to be overcome. It’s the most useful information you’ll get all year, and it’s free.

Care teams know what interrupts a shift, where information goes missing, and where a new process might quietly create risk. If people tell you something and nothing changes, they stop telling you. Then you have compliance without adoption, which is the most expensive combination there is.

We work on shift, including nights

You can’t understand a care service from a meeting room. Policies show how a service is meant to work. A shift shows how it actually works.

So we’re there. And we work nights properly, not a visit at eight in the evening.

Three in the morning, a first floor unit, two staff on. One is helping a lady back to bed who has been up twice already and is having a difficult night. A call bell goes at the other end of the corridor. Thirty seconds later an alert comes through on the handset for a third person.

Nothing has gone wrong yet. But every decision from here belongs to one person standing in a doorway, working out who needs her most and what can safely wait ninety seconds.

That’s the moment your technology either helps or gets in the way. It was almost certainly designed by people picturing a full team, a quiet corridor, and one thing happening at a time.

Night is also when care technology does its most important work. Unwitnessed falls. Long lies. Sleep disruption. The hours when the fewest people are awake and the most can go unnoticed. And it’s where training is thinnest, routinely squeezed into a handover.

Night teams don’t need a shortened version of your implementation. They need to help shape it, because they carry the hardest end of it.

We map what changes for every single role

A technology project has one business case. It won’t feel like one change to the people expected to make it work.

A care assistant is asking whether this adds a task to a shift that’s already full. A nurse is asking whether the information is good enough to act on. A registered manager is thinking about oversight, evidence, and what this looks like if she has to account for a decision. Maintenance will be the first call when something flashes red on a Saturday, and often wasn’t in the room when any of it was explained.

So we build an Adoption Map with your team. Every role in the service, across four questions.

Where several systems need to work together, we map the handovers between them too, because that’s usually where the gaps sit. You can see how we think about connected care technology across a whole service.

What actually changes on a shift?

Specific and physical. Not "improved oversight", but what someone will do differently before their round and at 2am.

What will they quietly worry about?

The column everyone skips, and the one that decides everything. Nobody raises it in a launch meeting. It shapes the rollout regardless.

How does this group actually learn?

Hands on, shown twice, written down, or in a first language that isn't English. Digital confidence varies enormously and rarely gets admitted out loud.

What does good look like at ninety days?

One observable behaviour per role, not a number on a dashboard. If you can't describe it, you can't tell whether it worked.

What you get

Practical things your team can keep using once we’ve gone. Where a team needs broader digital confidence rather than help with one system, our digital literacy training is often the better starting point, and we’ll tell you if that’s the case.

We work with whatever you've chosen

This is independent of what you’ve bought and who you bought it from. We’ll work on systems we had nothing to do with selecting, including ones from suppliers we don’t represent, as readily as on the technology we supply ourselves.

We’d rather help you get value from a system you’ve already paid for than sell you a replacement for a problem that was never about the product.

Why this matters now

Adoption of digital care records across CQC registered providers rose from 41 percent in December 2021 to 80 percent by July 2025. The sector has moved a long way in a short time. What providers tell government about the barriers is just as telling. We’ve written more about the shift from reactive to proactive care and where technology fits.

52%

Named staff training costs and high turnover as a barrier to care technology

39%

Named a lack of digital skills among staff, against only 34 percent naming staff reluctance

58%

Said upskilling the workforce was one of the things they most needed

Department of Health and Social Care, Findings from the 2025 Adult Social Care Provider Technology Survey, published March 2026, based on 1,085 CQC registered providers. An NIHR evaluation of digital care record implementation in England, published 2026, found implementation was too often suboptimal, naming inadequate planning, management and resourcing of change among the reasons.

Common questions

We've already bought the system. Is it too late?

No. A good deal of our work is with providers who are live and stuck. It’s usually easier than people expect, because the team already knows exactly what the problems are. Someone just needs to ask them properly, and then act on the answers.

Isn't this what our supplier's training covers?

Supplier training teaches people how the system works. It can’t tell your night senior what to do at 3am when two things need her at once, because that isn’t the supplier’s job and they’ve never worked your shift.

How long does it take?

It depends on the size of the service and where you’re starting from. Most engagements run across the rollout and the ninety days after it, because that’s the period that decides the outcome.

Do you only work with technology you supply?

No. We work with whatever you’ve chosen, including systems from suppliers we don’t represent. If you’re at an earlier stage and still deciding, Your Digital Journey is the place to start instead.

Will this take our team off the floor?

Very little. Most of what we do happens alongside people while they work, which is also where the learning sticks best.

Where this fits

Implementation and adoption sits alongside the rest of our consultancy work. If you’re not sure which you need, start a conversation and we’ll point you at the right one.

Let's have a conversation

Whether you’re planning a rollout or trying to rescue one, tell us what you’ve got, where it’s stuck, and what you hoped it would do. We’ll be honest about whether we can help.