Over the years, I’ve sat in rooms where the energy was electric, teams excited about new platforms, new pathways, new ways of “modernising” health systems.
I’ve also sat in very different rooms: GP surgeries where patients apologised for not knowing how to log in; community spaces where people admitted they were scared of “doing something wrong”; meetings where frontline staff felt buried under “yet another digital thing.”
Somewhere between these two rooms lies the real story of digital adoption, and this is where my entire perspective shifted.
It took time and thousands of conversations to realise something fundamental: People weren’t resisting technology. They were resisting the urge to feel overwhelmed, invisible, or left behind. The tech wasn’t the problem. The missing piece was empathy, the strategic kind, not the soft kind. The kind that transforms adoption by transforming how people feel.
Lesson 1: Empathy starts long before the tech arrives
Digital projects often begin with a solution. A platform is built. A product is procured. A rollout plan is drafted.
But the thing is, people don’t work that way. They have complex days, cultural contexts, lived realities, lived experiences, and if those aren’t understood, even the most brilliant piece of tech will struggle.
Empathy means asking different questions before anything launches:
● What does someone’s day actually look like?
● What barriers exist that we never see on a slide deck or in a data set?
● What emotional cost does this change carry?
Change doesn’t start with the tech, it starts with understanding the life it’s entering.
Lesson 2: Confidence is the metric we forgot to measure
We measure logins, uptime, usage, retention… But confidence? Rarely. Yet confidence is the quiet metric that decides everything, in my opinion. When people feel unsure, embarrassed, or “not techy,” adoption collapses before it begins. When people feel confident, they explore, engage, ask questions, and persist.
Confidence isn’t optional. It’s the foundation of digital behaviour change. Maybe this is where we need to be braver as a sector. We measure clicks, logins, activity, and uptime, but almost none of our dashboards measure how people feel.
Imagine if empathy itself became a KPI. Not something vague and philosophical, but something we could track. Things like confidence gained, barriers removed, trust built.
If we build empathy into the metrics, then empathy will finally show up in the outcomes.
Lesson 3: Empathy is not an add-on. It’s architecture.
Empathy is not something we sprinkle on top of a rollout. It should be woven into:
● The way we design
● The way we communicate
● The way we train
● The way we measure success
● The way we show up in communities
If empathy arrives at the end, it’s already too late. Which makes me ask:
We have digital training.
We have transformation training.
We have product training.
But where is the digital empathy training?
Because no amount of innovation replaces understanding how people feel, we don’t need more digital tools; we need more digital understanding.
Across the UK, the UAE, and globally, one truth keeps resurfacing: the technology solutions that work are those built around people, not processes. Every successful adoption I’ve witnessed had empathy at its core, not as a buzzword, but as a way of working. Digital adoption isn’t about pushing tech. It’s about aligning with human reality, and that is where true transformation begins.
Here are tangible, practical things you can start weaving into your own digital programmes. These are things that don’t require extra budget, just a shift in how you approach your work.
1. Bake empathy into the discovery and design phase
Before writing a strategy or designing anything, try to add these two steps:
a) A “day in the life” walkthrough
Speak to 5–10 real users and ask them to describe their day. Map their emotional peaks and dips.
b) A barriers scan
Identify cultural, emotional, logistical, and confidence-based blockers, not just the tech ones. This will immediately change the entire solution trajectory.
2. Introduce a “human impact check” in every decision you make
In every meeting or workshop, ask:
● Who gains confidence from this?
● Who might feel left behind?
● What emotional friction have we created?
It’s simple and it’s quick. It instantly improves decision quality.
3. Create ‘micro-support’ moments
Not everything needs a complete training programme. Some of the highest impact interventions are tiny:
● Two-minute explainers in plain, simple language
● Quick demos during lunch shifts
● Screenshots with circles and arrows (there are excellent AI tools out there that can even scribe for you!)
● A safe space for “silly questions”
What you will realise is that these small signals of support build a strong sense of psychological safety for users.
4. Start collecting empathy-led data
Alongside your KPIs, add three simple metrics:
● Confidence before vs after
● User-reported barriers
● Perceived value (“How much does this help you?”)
These become powerful indicators of where adoption will thrive or fail.
5. Advocate for co-design, not consultation
This is the difference between “We asked them what they think” and “We built it with them”.
Bring users into decisions early, genuinely, not as validation, but as collaboration.
6. Meet your users where they are
It’s important to realise that not everyone will attend your training. Not everyone will read your emails, and not everyone wants a webinar.
Think about meeting people in:
● Community spaces
● Staff rooms
● Ward corridors
● Schools
● GP waiting areas
Digital adoption increases the moment digital feels familiar.
7. Translate features into human value
When you describe your digital technology, don’t talk about what it is. Talk about what it does for someone. For example,
● “This saves you 10 minutes every morning.”
● “This reduces the number of times you have to repeat your story.”
● “This helps you spot asthma triggers earlier.”
Humans adopt benefits, not features.
8. Remember that empathy isn’t just about adoption, it’s about design
Before any line of code is written, ask: “Have we mapped the human journey?” If not, pause.
Design Thinking, behaviour insights, and human-led discovery should shape every digital product before a single feature is agreed upon.
Empathy at the end is damage control. Empathy at the beginning is a strategy.
As I conclude, a question I like to leave others with when reflecting on all of this is if empathy were a measurable KPI in your work/programme, what would success look like? In fact, what would that KPI look like? What would it change? Because in my experience, technology changes systems, empathy changes lives. Where they both meet, that’s where transformation finally begins.
