Moving forward without starting from scratch
Around the world, Microsoft Dynamics AX projects share one common reality:
A large share of them do not go as planned. Sometimes the budget is overrun, sometimes users do not adopt the system, and sometimes the project seems to be working but never delivers the real benefit. At that point, the first reflex in most countries is the same: "Let's start again."
In recent years, however, that reflex has been seriously questioned, particularly in Europe and North America. Starting a completely new ERP project brings not only licence and consultancy costs but also lost time, organisational fatigue and reputational risk. That is why many companies have started to take a different path with failed AX projects.
1. Analyse the situation, not the system
The first approach that stands out is to analyse the current situation calmly instead of blaming the system.
Which modules actually work?
Which processes are getting stuck?
Why are users going back to Excel?
Is the difficulty technical, or is it about management?
Any decision to "start again" taken without this analysis can deepen the problem rather than solve it.
2. Small, effective interventions instead of big changes
The second important approach seen in international examples is small but targeted interventions.
Rather than transforming the whole system, companies first deal with the critical bottlenecks. The areas at the heart of the business, such as general ledger, inventory, production or reporting, are stabilised first. That way the ERP becomes part of daily work again within a short time.
3. Redefine project ownership
Another problem common to failed AX projects is the lack of clear ownership. Companies facing this deal with project management before the technical solution. Roles are clarified, expectations are made realistic and communication is simplified. More often than not, it is this clarity in management that gets the ERP back on its feet.
4. A "rescue" culture
In Germany, the Netherlands and the Nordic countries in particular, "ERP rescue" is now treated as a discipline in its own right. The aim is to protect the investment already made, avoid wearing out the team and make the project sustainable. This approach sees failure not as a label but as a natural phase of a project.
In short, the message from around the world is this:
An ERP project does not have to start perfectly. What matters is being able to stop at the right point and redirect it. Understanding the existing setup and moving forward calmly and to a plan, rather than starting from scratch, can turn Dynamics AX projects back into systems that create value.