ERP projects don’t fail because of tech – they fail because we forget the people

I’ve worked on Microsoft Dynamics 365 ERP projects for over a decade, and I’ll tell you this: I’ve never seen a project fail because of the software.

And if there’s one thing I’ve learned, it’s this: You can’t expect users to transform how they work and run a full-time job and navigate a new system – not without support.

That’s where projects start to slip. And that’s where I step in.

ERP can’t be run on the side

One of the biggest pitfalls I see is when companies try to run the ERP project on top of daily operations. Users are asked to join workshops, test configurations, rethink how they work – all while doing their regular jobs.

Of course they get tired. Confused. Defensive.

And then comes the phase I’ve seen too many times: decisions get made in a rush. People stop speaking up. Assumptions creep in. And suddenly, that “strategic transformation” becomes a survival game.

It doesn’t have to be this way. With the right support, the pressure goes down. The clarity goes up. And people feel part of the solution – not the problem.

The system should shape the process – not the other way around

Another common trap: trying to build the new ERP around the old way of working.

I get it. Change is uncomfortable. And your current processes have kept the business running for years. But the truth is: you don’t invest in ERP just to do what you’ve always done – with a shinier interface.

You do it to work smarter.
To automate repetitive tasks.
To give people more time for the work that really matters.

At adesso, I’ve helped organizations redesign financial processes, connect fragmented finance operations, and structure ERP so that it truly supports everyday work – not just system requirements.

And that’s based on real projects, not just theory.

Real moments from real projects

Client had no internal ERP lead. People were overwhelmed. We stepped in, brought structure and focus, realigned the roadmap, and prevented problems before they grew.

Client had chosen the system but didn’t know what it should enable. We clarified business goals, defined key scenarios, and saved weeks of rework.

In some cases, we’ve even helped before a system was chosen – comparing solutions, facilitating vendor-neutral assessments, and helping companies invest wisely.

These are actual adesso projects I’ve supported. Different industries, similar challenges – and the same goal: delivering real value with ERP.

My role: Supporting the customer, end to end

I work for the business – to help ensure the ERP project delivers the best possible outcome for the customer.

That means:

Translating business needs into system language
Supporting users in understanding what change really means
Acting as the customer’s sounding board, guide and sparring partner
Helping extract maximum value from the ERP investment
Making sure the project reaches the finish line successfully

ERP should work for you – not the other way around.

Final thought

ERP projects don’t fail because of software. They fail when people are left alone – and when no one’s looking after the business side of the transformation.

If you're in the middle of an ERP project and need help getting back on track – or planning one and want to start strong – I’m happy to talk.

Author Jukka Osanen

Jukka works as a Senior Solution Architect at adesso Finland. With a deep background in finance and a sharp eye for system optimization, Jukka is working with global D365 Finance implementation projects, ensuring that solutions are designed smartly and take full advantage of the system's capabilities.

Category:	Architecture
Tags:	Architecture Microsoft Solution-Architecture Enterprise Architecture Dynamics 365