There’s a pattern we see time and time again.

A business commits serious budget to a new HR platform, ATS, VMS or a full multi-faceted transformation. These implementations vary in value and time to deploy, but the intent is always right

• Improve consistency
• Increase visibility
• Better data, better experience
• Drive efficiency
• Modernise how HR works

But somewhere between the idea, the ambition and the outcome… things drift. Not in a dramatic, visible way. Nothing obviously “fails’, but quietly, underneath the surface, the transformation starts to lose shape.

Not because of technology or vendor failure, but because the transformation was never clearly anchored in what needed to change for your people.

The focus stays on systems, features, timelines, and configurations, while the real question goes unanswered:

What will change in how people work, decide, and behave every day?

This is where transformations begin to unravel. They start with a system decision, not a change strategy, where leaders align on vendors, features, cost, and timelines, but miss the one thing that matters most: how the change lands with their stakeholders.

Because stakeholders don’t need more system detail, they need translation of the plan. They need upfront clarity on:-

1. Who is affected - which roles, teams, and stakeholders will experience change?
2. Why this is happening - what problem are we solving, and why does it matter to them?
3. What is changing - what will people do differently, and what stays the same?
4. When it will happen - when will the change land, and when should they act?
5. Where it shows up - in which processes, systems and moments that matter in the employee journey?
6. How it will work - how the change will be delivered, embedded into daily life and how supported.

Transformation is not what system you implement, it’s what your people do differently.

When people don’t understand the change, they don’t adopt it. And when they don’t adopt it, the transformation doesn’t really happen, it just exists on paper.

The Trap: Transformation without Translation

On paper, everything looks like progress: the RFP is launched, vendors are shortlisted, demos are done, and a decision is made. But underneath, alignment is weaker than it appears. HR leaders are unclear on impact, regions interpret the change differently, executives assume risk is controlled without defining success, and IT and Finance align on cost rather than outcomes. Different parts of the organisation believe they’ve agreed the same thing, when in reality they’ve each agreed a slightly different version of the future.

If people change is not factored in, the organisation fills in the gaps itself…

What should happen instead is quite simple, but it requires doing it earlier than most organisations are comfortable with.
Shaping the why and how of change, and building trust before commitments are made, reduces early resistance.

And if that doesn’t happen?
You don’t just get resistance later, you get organisational and technology misalignment baked in from day one.

Late Engagement in Change

One of the most important elements of change is ensuring that it is considered a vital workstream from day 1 of the transformation, not day 1 of the implementation. The moment the decision is made to change the tech landscape.

When we’re brought into programmes that are struggling through patchy adoption, resistance, unrealised ROI, the root cause is rarely technical. It’s usually that change was undefined early on, executive engagement dropped away after selection, and key design decisions were made without the real users’ input.

Technology Doesn’t Fail, Adoption Does.

In most cases, the vendor delivers exactly what was asked for. The system works. The workflows are there. The functionality is live.

Most vendors provide minimal change management, or none at all. And even when it’s included, it’s often generic. Getting change management wrong isn’t unusual, it’s actually the norm. The mistake organisations make is assuming it’s covered, when in reality it needs to be owned internally.

But what if your people don’t change?

We’ve seen global HR systems go live on time and on budget, only for regions to continue running local processes in parallel six months later.

And when they don’t, workarounds appear, old processes continue, your data becomes inconsistent and confidence drops.

We often hear the same phrases at this point:
“We still do that in Excel.”
“The team don’t really use that module.”
“We don’t fully trust the data.”

Research has consistently shown, that as much as 70% of implementations face adoption challenges, not because the systems don’t work but, because of organisational adoption challenges.

The £££ Reality

This is where the trap becomes expensive. Without structured change factored early..

• Systems go live but are underused
• Productivity dips during transition
• Support requests spike
• ROI is delayed, or never realised

The most expensive system is one that isn’t fully used and yet, change management is still one of the first things reduced or removed to protect budget, with the assumption that people will “get on board.”

Organisations are effectively “betting” their investment on people naturally adapting

Where Most Transformations Go Wrong

We see the same pattern showing up repeatedly:

1. No clear narrative early

No shared story for why this change is happening now
→ Stakeholders create their own version

2. Executive alignment is assumed, not defined

No clarity on:

• Decision principles
• What success looks like
• What trade offs are acceptable

3. Change is positioned as “later”

Instead of something that:

• Starts at selection
• Shapes design
• Protects adoption

4. Stakeholders are told, not engaged

Instead of:

• Real world conversations
• Capturing their real daily constraints
• Building trust early

What Good Actually Looks Like

The difference is not more activity. It’s better timing. The real goal?

The organisation is ready before the system arrives

• Leaders who can clearly articulate why the change is happening
• HR teams who understand change will be phased
• Regions feel heard and engaged
• Leaders are aligned on success
• No surprises when implementation starts
• People know what’s changing

The best programmes make the change visible. They give it a project name, a story or a brand. Not for decoration, but to signal that this is something different, something phased, and something people are part of, not something being done to them.

The Shift: From Transformation to Adoption

The organisations that avoid the trap do one thing differently. They treat change management as part of the product, not an add on

They understand:

• Implementation puts the system in place
• Change management ensures it’s actually used

And more importantly, they recognise that adoption is not a phase at the end, it’s something you build from the very beginning.

Final Thought

Most HR transformations don’t fail loudly. They fail quietly and over time. The system works, but the organnisation never really changes. You’ll recognise it if you’ve been through it:

• low adoption
• inconsistent processes
• manual workarounds
• missed ROI
• frustrated teams

That’s the Transformation Trap.

How Udder can help

And if you’re seeing these signals already, or you’re about to start a transformation the question isn’t whether change management matters. It’s whether you have a clear view of how your organisation actually operates today.

Because without that, you’re not designing change, you’re guessing.

This is where we typically support clients. Not just with change delivery, but by stepping back and understanding what’s really happening across your tech, your processes, and your people.

A structured tech audit gives you that baseline; what’s working, what’s not, where adoption is breaking down, and where value is being lost , so your transformation (or recovery) is grounded in reality, not assumption