Systems don’t burn out, people do

Someone in your team says:

“Why are we changing our system? We all know how to use the one we have, and it works ok.”

That moment matters just as much, sometimes more, than the ERP architecture design itself.

Or when you notice your project stalling because actions don’t happen, decisions take longer, energy in workshops drops. It could be an operational or planning issue. Or it could be a build-up of resistance, overwhelm or fatigue in one or more of your team.

Sometimes it’s even simpler than that.

The person who designed or manages the current system may feel a quiet sense of ownership. It’s their work. Their expertise. Their reputation. If the new system replaces what they built, they don’t just need training - they need confidence that the new system is up to scratch. If that confidence isn’t built, quiet resistance can form, not from incompetence, but from identity protection and a drive to protect the business.

This dynamic rarely shows up on a risk log. But it can show up in your lead sponsor losing confidence in the programme, and it will slow progress more than a technical defect.

How transformation resistance can build

Change isn’t a single event anymore, it’s cumulative. New systems. Evolved reporting. Additional controls. Greater expectations. More micro-actions to get done. All layered over existing pressure.

When that load isn’t recognised and managed, overwhelm grows, resistance rises and momentum slows. Not because the goal is wrong, but because the people carrying it get exhausted. And exhausted teams can’t optimise, don’t advocate, and struggle to sustain momentum after go-live.

Implementing new technology is often the right thing to do. It creates efficiency, improves capability and underpins scale. The ambition isn’t the problem. It’s how the change is led.

In ERP and digital transformation, the technical architecture is usually designed in detail. Governance is mapped, timelines are built, and risks are tracked. But very little attention is given to how change will be experienced by the people living through it.

Even if the system is technically “perfect”, buy-in and sustained engagement determine whether it delivers value. And sustained engagement depends on energy, trust and leadership behaviour over time.

That’s where emotional intelligence becomes critical.

Emotionally Intelligent leadership in action

Emotional intelligence (EQ) isn’t about being nice. It isn’t about avoiding tough decisions. And it isn’t a soft layer of change management added at the end.

It’s the ability to recognise what you’re feeling, regulate it and choose how you respond. It’s also about sensing the room and understanding how others are experiencing the shift.

Leaders name pressure when timelines tighten instead of pretending everything’s fine.

They listen before deciding. When users push back, that’s often signal, not resistance.

High EQ leaders adjust pace when needed. Not every concern requires slowing down, but ignoring overload creates disengagement.

They communicate tough moments clearly and with empathy. People can handle difficult decisions, what they struggle with is confusion.

And in high-pressure moments, they model stability. If leaders react emotionally, that spreads. If they stay calm and deliberate, that spreads too.

ERP transformation isn’t a project with a clean end point anymore, it’s part of a continuous operating model. Leadership capability must evolve alongside technical capability.

Technology architecture enables capability. Emotional intelligence protects momentum, resilience and long-term value. Without it, even the best systems risk under-performing. The future of transformation doesn’t belong to technology alone, it belongs to the leaders who can guide people through it.

Want to learn more about leading successful technology transformations? Get in touch with us to discuss how to protect momentum and build engagement, or follow us on LinkedIn for more tips, guides, and insights on people-led change.