Less about technical problems, more about management realities
Microsoft Dynamics AX 2012 is a powerful ERP platform that has been the backbone of many businesses for years. It is still in active use at many companies and, when managed well, makes a real contribution to business processes. Even so, a large share of AX 2012 projects stall over time, and the system stops delivering the expected value.
The root cause is usually not the software itself. Because Dynamics AX 2012 is so flexible, it gives the impression at the start of a project that it "can be adapted to anything". Without proper control, that flexibility leads to excessive, unmanaged customisation. Over time the code base grows, the system becomes complicated and every small change turns into a serious risk.
Another important cause is that documentation gets pushed into the background during the project. When the functions developed, the customisations made and the decisions taken are not properly recorded, knowledge is lost as soon as the project team changes. That creates uncertainty for the people using the system and a serious dependency risk for the teams supporting it.
A further problem often seen in Dynamics AX 2012 projects is the gap between business processes and the system. The business changes, grows or shifts direction, but the ERP stays where it was. Process designs that are not kept up to date force users to work around the system and come up with their own alternatives. At that point the ERP stops being a tool that makes work easier and starts to be seen as an obstacle.
On top of all this, project management in AX 2012 projects tends to weaken over time, which speeds up the stall. When the system is considered "finished" after go-live, no culture of continuous improvement and ownership develops. Yet an ERP project is a living structure that still needs managing after go-live.
A stalled Dynamics AX 2012 project is not inevitable. When the existing system is analysed properly, customisations are simplified and processes are brought up to date, AX 2012 can keep running reliably for many years. What matters is to take a fresh look at the project instead of blaming the system, and to restore the balance from the right starting point.