Skip to Content
Best Practices

Digital transformation rarely fails due to bad software

It fails because people, process, and technology are not aligned. Here is how to spot the misalignment before it costs you 18 months and a budget.

Most digital transformations fail before the software is even installed.

I speak with manufacturing directors across the UK who have just invested heavily in a shiny new system that is going to "fix all our problems." The boardroom is thrilled. The vendor is thrilled. The implementation partner has a press release ready.

But walk onto the actual factory floor and the team is still quietly running the business off multiple chaotic Excel spreadsheets that Geoff implemented just before he left five years ago. The new system is technically deployed. Nobody is using it. Nobody told the boardroom.

"Technology is one third of the equation. The other two thirds, people and process, are what most projects skip."

Why alignment is the bottleneck in 2026

ERP vendors are knocking. AI is being pitched as a shortcut around the messy organisational work. PLM is back on every boardroom agenda. The temptation to buy first and align later has never been bigger.

But the cost of that mistake has also never been higher. UK manufacturers are losing experienced operators to retirement and to competitors. Every month the new system sits unused is a month where the workarounds get deeper and the gap between what the boardroom thinks is happening and what is actually happening gets wider.

The boardroom and the factory floor, having different conversations

The boardroom view. The new system has been live for eight months. The implementation partner reports green status. The CFO sees the licence cost. The MD assumes the operational efficiency gains are starting to land.

The factory floor view. The new system logs in slowly. It does not handle the kind of part numbers we actually run. The screen we need for daily standup does not exist, so we still print the spreadsheet from Geoff's laptop and pin it up.

The gap. Eighteen months later, the gap surfaces in a board meeting when productivity numbers stop moving. The transformation is declared "ineffective," the system is blamed, and the cycle restarts with a different vendor.

The miss. The software was never the problem. The problem was that no one had aligned the people and the process around using it before the rollout started.

Technology is one third of the equation. The other two thirds are what most people skip.

Every successful transformation I have been part of in 20 years of UK manufacturing comes back to the same three-legged stool: people, process, technology. If one leg is shorter than the other two, the stool wobbles. Skip a leg entirely and it falls over.

Most projects skip "people" because it is hard. Briefing the workforce, training them, listening to their objections, redesigning the role around the new system — none of that fits neatly into a Gantt chart. So it gets compressed into a one-day handover at go-live and called "change management."

Most projects skip "process" because it is uncomfortable. Mapping how the business actually works, instead of how the org chart says it should, surfaces decisions that have been quietly avoided for years. So it gets reduced to "the vendor will recommend best practice" and the existing mess gets digitised.

Technology is the only third of the equation that can be procured. So that is the third every project leads with. And then is surprised when it does not work.

What we would tell you if we were sat across the table

If you want your next digital transformation to actually land, these four things will make more difference than the choice of software.

Map your real process before you procure. Not the org-chart version, the actual version. If you can fit it on a whiteboard, you understand it. If you cannot, you are not ready to buy anything.
Bring your workforce in before the vendor demo, not after. The people who will use the system every day should help shape the brief. If they only see it at go-live, you have already lost.
Kill the workarounds you can. Document the ones you cannot. Every workaround is information. It tells you exactly where your existing system fails the people doing the work. Take it seriously.
Measure adoption, not deployment. "We deployed the module to 800 users" is a vanity metric. "The shift supervisors use it every morning instead of the spreadsheet" is the only metric that matters.

Worried your transformation is heading for the spreadsheet drawer?

We run discovery sessions with UK manufacturing teams to surface the misalignment before it costs you a budget. Half a day, your team, a whiteboard, and an honest look at where the gaps really are.