The human factor in digital transformation

I've lived through digital transformations in banking with ING, in pharma with Boehringer, in hardware with HP, in fintech with Block and in energy with Holaluz. And in consulting with Amaris I've seen them from outside, in very different clients. The conclusion, after years, is uncomfortably simple: the technology works, the people are where the challenge lies. When transformation fails, it's almost never because of the software. It's because of how the people who had to adopt it were treated.

This article isn't another toast to "change management". It's an attempt to put useful words to what almost nobody names and what decides the outcome.

What digital transformation means to a real person

When transformation arrives, the speeches talk about efficiency, productivity and the future. What the person in their seat receives is: a new tool they don't master, a process that changes just when they had finally learned the old one well, uncertainty about whether their job will still be needed, and the feeling that someone decided all this without asking them.

If transformation doesn't account for that subjective experience, the human response will be defensive, even if the person denies it. There will be hidden slowness, passive sabotage, strange errors, silent disengagement. And nobody will connect it to the transformation, because officially "everyone is aligned".

The three implicit questions

Every employee, facing a digital change, asks themselves three questions. Almost nobody verbalizes them, but every head turns them over.

• Does this change my job security? (Fear)
• Does this change my professional identity? (Belonging)
• Does this change the respect I receive? (Self-esteem)

A transformation that answers these three questions honestly and early frees up energy. One that ignores them consumes energy.

Change isn't managed, it's accompanied. Whoever manages it like a technical project generates resistance. Whoever accompanies it like a human process unlocks commitment.

The three typical mistakes from leadership

I've seen enough projects to have watched these three top-down mistakes repeat.

1. Communicating as if everyone were an executive

The message at the committee makes sense for the seven people in the committee. Pushed unchanged to staff, it only triggers distrust. The phrase "we're going to be more efficient" coming from a senior executive automatically translates, in the breakroom, as "they're going to lay people off". Sometimes it's true, sometimes it isn't, but it's always read that way if it isn't clarified directly.

2. Underestimating the emotional cost of change

Transformation plans have line items for licenses, for consultants and for infrastructure. They usually don't have line items for emotional accompaniment, for unpressured learning time, or for the productivity loss of the first quarter. When that line item doesn't exist, those costs happen anyway, but they show up disguised as resignations, mistakes and turnover.

3. Confusing training with adoption

Sending people to a four-hour course isn't transformation. It's having a clean conscience. Real adoption requires sustained accompaniment over months, not a one-off impact.

What does work, from my experience

I don't have magic recipes. I have practices I've seen produce sustained results.

Talk to the skeptics before the enthusiasts

The executive's instinct is to look for the enthusiasts to pull the cart. My contrary instinct, learned through screw-ups, is to listen first to the skeptics. The enthusiasts usually pull anyway without being pushed. The skeptics, if genuinely heard, go from silent saboteurs to honest collaborators. And they bring information no enthusiast gives you, because they see problems the others don't want to see.

Design real quick wins for the most exposed

Identify the people the change unsettles most and design a small but valuable quick win for them in their first two weeks. Something that saves them time or eases an annoying task. This shifts the internal narrative from "this is so we work more" to "this at least takes that off my plate".

Allow grief for the previous process

I know it sounds like therapy. That's because it is. People who have done a process one way for ten years are attached to it. When a tool comes that changes that process, there's a small loss almost no one allows them to express. In transformations that have gone well, I've seen leaders give explicit space for "what we'll miss about the old system". It's a brief ritual, but powerful. It clears the nostalgia and frees people to embrace the new.

Bet on peer-to-peer, not on formal cascade

The colleague next to you has more credibility than the external trainer. Identify 5-10 natural champions (not appointed, but those already experimenting), give them time and recognition to help their peers, and let the diffusion be horizontal. This multiplies the speed of adoption and reduces the emotional cost of change.

Middle leadership: the ignored bottleneck

The executive decides. Staff executes. And in between, middle managers take all the bullets. If they're with the change, everything flows. If not, everything jams, and nobody usually knows why. Digital transformation that doesn't specifically support middle managers is doomed to invisible friction.

What middle managers need

• Honest, early information, before it leaks through informal channels.
• Time to absorb the change before having to defend it.
• Spaces where they can express doubts without being labeled as resistant.
• Concrete support for the difficult conversations with their teams.

Skipping the middle manager (communicating directly to staff in mass events) can feel like agility, but it undermines the authority of those who have to sustain the day-to-day. It's one of the most underestimated levers and, also, one of the most easily broken.

The executive's own role in their own transformation

There's a delicate point: the executive who asks others to change without changing themselves loses all moral authority. If you ask your staff to use AI every day and you open it once a month, your team notices. And they stop taking the speech seriously, even if they keep obeying on the surface.

The serious executive gets into the new tool. They make their learning curve public, share their mistakes, ask for help. This, which in hierarchical cultures usually feels scary, is what generates the most trust and accelerates real adoption the most.

The mistake I see most often

The mistake I see most often is treating people as resources to align, instead of as subjects living through a change. Plans talk about "stakeholders", "audiences", "segments". But there are people with families, mortgages, fears and professional pride. When they're treated as cogs, they respond like badly oiled cogs. When they're treated as people, they usually contribute more than was asked.

The rule I apply: in every transformation project, before the first official communication, I spend at least one day listening individually to 8-12 randomly chosen people across levels. No formal agenda, with the question "what worries you about what's coming?". That information, mixed with data and observation, is what lets me design a plan with real chances of working. Without that, everything else is theory.

Digital transformation without the human factor is a technical project that fools itself. What builds an organization capable of continuing to transform itself is the awareness that change happens to people, and that people need time, listening and respect. Technology changes fast. Human capacity to absorb change changes slowly. Honoring that pace isn't weakness, it's the only path to make transformation sustainable beyond the first year.