Are current Microsoft Dynamics AX implementation methods obsolete?

I'm amazed that an industry that prides itself on improving processes and controlling waste is not more introspective. Having been an implementation consulting for 25+ years, I have observed ERP project implementation methodologies and staffing plans stagnate even as the software, both its capabilities and deployment models, have evolved along with the broader business landscape. The result has been a range of mismatches for customers: in how systems are deployed, how projects are staffed, and how clients and partners foster a productive working relationship.

Here, I am attempting to write about some of these challenges, both for the Microsoft Dynamics AX or Dynamics 365 for Operations consultant and for the user.

Buying habits in the Dynamics AX world

It is interesting to see how companies typically select an ERP system. The journey is undertaken to pick the best software for their needs. That sounds perfectly reasonable, but many things go wrong.

Often the first issue is, how do clients quantify their needs, and the best software for them?

The first process they use is some form of RFP. This is a series of questions with the attempt of culling out software that does not meet the company's needs. These have become more of a process of test taking skills. A vendor will not go through this process unless they are desperate or believe they have a good chance to win. The less the client is truly invested in understanding the product and company, the greater the prospect of not getting a successful outcome. You cannot abdicate this responsibility to a third party.

They decide based on demos, which are ...