Six Basics of Preventing Pain in Your ERP Implementation

"Simplicity is the ultimate sophistication." -Leonardo DaVinci

Over the last decade of being involved with customers and implementation partners for ERP projects, I simply cannot overstate the above sentiment - if you keep everything simple, you make an ERP project smooth and constructive.

Let me explain further. I remember hearing multiple horror stories related to heavy solutions like SAP and Oracle including implementation failures, busted budgets, law suits, and other negativity. It is contrary that the ERP project is aimed at easing organization's way of working ends up being another pain itself.


Requires FREE Membership to View

Become a Member Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also receive periodic email newsletters with the latest relevant articles and content updates.
About Raman Dhooria
Raman Dhooria works with Microsoft Dynamics in India and takes care of key partner ecosystems. Prior to Microsoft, Raman worked in South East Asian and the UK markets on SAP, Oracle and BaaN. Raman has an MBA in marketing and a bachelor's degree in Mechanical Engineering. He is the author of "SMB Guide--The Road to ERP", which is available online. He also writes a Dynamics blog.

Read full bio...

Nice article


Nice article and thanks for sharing, the points are very clearly defined. Nowadays in the market Implementation partners not are looking at customer requirements and pains deeply, poor documentation and inexperienced consultants which lead to Implementations getting fail.

Microsoft should Initiate every implementation should pass through Microsoft-QA that will improve the Implementations (Make sure all requirements & Deliverables covered) successfully and customer satisfaction.

Nice helpful information. As

Nice helpful information.

As for point 3, I believe its hard to control or ensure that the team will remain as is.