Big4Guy writes a blog on big software deployments. His posting on Five Common ERP Implementation Pitfalls has the ring of truth for me, so here they are:
- Pin-pointed clarity as to why we are going in for an ERP. What are the synergies that we expect, how will the new system SAP / Oracle / JD Edwards change our present way of working. Clarity in this regard is the one most important factor.
- What is the implementation strategy. Are we implementing in a phased manner or a big bang implementation. Big bang implementation where all modules of an ERP AP / AR/ GL/ etc are implemented all at once is bound to fail if not properly planned.
- How much time have you allocated for testing your system. Testing will include testing the design as well as the performance of the system.
- What investment have you made in your hardware infrastructure. When investing in hardware it is generally safe to go in for a higher configuration so as to take care of processing loads later on.
- Have you involved all critical users in the process flow and business process design phase. If the users are not involved right from the start, it is a sureshot sign of a ERP failure. Understanding the users point of view POV is very important for successful ERP implementation.
I suspect this guy has been through some battles and speaks from knowledge and experience.