ERP Failure: It’s a people problem.

ERP failure isn't a technology problem. It's a people problem.

Ask anyone who has been through a difficult ERP implementation what went wrong, and you'll hear a lot of different answers. The system wasn't configured properly. The data migration was messier than expected. The go-live timeline was too aggressive.

But dig a little deeper, and most of those answers point to the same underlying cause.

The system worked well, but the people weren't ready.

The uncomfortable truth about ERP projects

At 3EN Group, we continuously research better ways to deliver business transformation for our clients, as part of that research, paired with the experience that our team has, we have learned that the majority of ERP implementations (NetSuite or otherwise) that underdeliver, rarely do so because the software is the problem.

The problem is most always human.

Regardless of selecting a mature, powerful & well-proven platform, your ERP implementation may still not deliver to budget, to deadline, or provide expected return on investment. The problem more likely stems from resistant department heads who were never properly brought along the journey, finance teams who were trained once and then left to figure it out themselves, or sales teams who reverted to their own spreadsheets because the CRM felt unfamiliar and nobody was around the help.

What change management actually looks like

Change management is one of those phrases that gets used a lot and understood a little. So, let's be specific about what it means in the context of an ERP implementation.

It means identifying, early, which people in your organisation are going to find this change hardest, and why. It means building a communication plan that keeps stakeholders informed without overwhelming them. It means running training that fits how your people actually learn, not just ticking a box. It means having someone available in the critical weeks after go-live who can sit with a confused user and work through their questions in real time.

It means understanding that your Head of Finance has been doing things a particular way for eleven years, and that asking them to change everything at once is going to require more than a one-hour system demo.

None of that is a technology problem. All of it requires a human being with the emotional intelligence, patience, and experience to navigate it well.

The moment resistance becomes visible

In our experience, resistance to change rarely announces itself. It doesn't show up in a project risk register or get flagged by the new system.

It tends to show up closer to go-live, after most of the implementation work has been done, and suddenly you hear that one of your departments may not be ready. Or in one of the final training sessions, when zero-to-one person is asking a question and you struggle to ascertain if everyone else is engaged.

In some cases, it can be overlooked internally until post-go-live support, where the support desk is full of tickets from people who now must use a system, they are not comfortable with at all and can’t figure out how to do their daily tasks in a more pressured environment.

At this point, you could have invested in a system that has the ability to provide a more than satisfactory return on investment, but a team that is not sure how to realise it.

This is where your implementation team can come into play.

An experienced consultant delivering the training, a PM who is reviewing the pre-go-live red flags, or the support rep reviewing your ticket load, will all be able to flag with your team where things may go, or may have gone wrong. They will be able to tell you if they feel that certain team members aren’t as invested, aren’t ‘getting it’ or seem to be struggling with the training. They can advise additional post-go-live training and help you get back on track of having a team and system that work in harmony.

If the people are the problem, can we replace them with technology?

It’s a question that is at the forefront of so many minds right now. With AI rapidly evolving over the past few years, it makes sense to ask if the human part of the implementation is causing the problems, can we not remove that reliance?

AI tools are getting remarkably good at a lot of things, and can benefit an ERP implementation if used well, in the right areas. But it is not good at sensing the mood in a room. They cannot tell the difference between a stakeholder who is genuinely engaged and one who is nodding along while mentally planning their own workaround. They cannot build the kind of trust that makes a resistant Operations Manager decide to give the new system a proper chance.

These are fundamentally human skills. They require presence, empathy, and the kind of experience that only comes from having navigated the same dynamics on previous projects.

A consultant who has delivered fifteen ERP implementations knows that the Finance team's concerns about month-end reporting need to be addressed before they'll commit to the system. They know the best time to surface adoption risks and know which conversations to have, with whom, and when.

That knowledge isn't in a dataset. It's in the person.

The cost of getting the people side wrong

If you're evaluating implementation approaches purely on cost and speed, it's worth understanding what the alternative looks like in practice.

A system that goes live on time but isn't properly adopted doesn't deliver its ROI. It generates a constant stream of support tickets. It creates shadow processes such as the spreadsheets that people run alongside the system because the people don't trust it. The system will become a source of frustration rather than efficiency, and over time, it becomes the thing your business works around rather than the thing that supports your business.

The investment in proper change management, in human expertise that keeps your people engaged, informed, and genuinely ready for the new way of working, is not an optional extra. It is the difference between an ERP that transforms your business and one that becomes an expensive footnote in your annual review.

What ‘good’ looks like

The best implementations we've been part of share a common thread -  they put people at the centre from day one and view change management as a genuine priority that shapes how the project is designed, communicated, and delivered.

This means having experienced human beings, both internally and within your ERP partner, leading the implementation. People who understand that the most important thing they're implementing isn't a system, it's a new way of working for your whole organisation.

It means engaging in conversations that go beyond process documentation and get into how your teams actually feel about change, encouraging stakeholder engagement that builds genuine buy-in rather than grudging compliance and training formats that are built around your users.

It means clear communication between your internal team, and your project delivery partner which addresses the human impact that system implementation and business transformation can have, at the start, middle and end of each project.

It means, you will see results from day one.  

If you want to start planning your business transformation project, and a new ERP is part of that list - reach out to one of our experts today, to see how we can help you achieve ROI from the get-go.