Free white paper
ERP Implementation: 11 Steps to Success
The 11 Proven Steps You Should Know About ERP Implementation
It’s easy to tell when some things in life are ready. A tomato turns red when it is ready to pick. A baby stands without support when it is ready to walk. An airplane closes the doors and taxis away when it is ready to fly. Unfortunately, determining if a company is ready for ERP is not nearly so straight forward. Testing for ERP readiness is somewhat like arriving at a medical diagnosis – you accumulate a list of symptoms, and see how many ERP would cure. The following are some of the symptoms you should look for.
The most compelling clue for ERP readiness is that it is the people from the business units who are asking for it – not IT. This is normally because business models have evolved to the point where many are literally painful. This is the result of a Catch-22: new business models are undertaken to support growth; because of that, they start small; because they are small they cannot justify an IT investment to accommodate the business model; because there are no computer systems to support the new business model, it is not scalable; growth objectives are never realized, and the only recourse is to create additional business models to make up for the shortfall.
Another symptom is that the risk of an obsolete system failing, or a legacy program failing to prevent fraud, or of a functioning system growing so complex that it occasionally produces embarrassingly erroneous results, is greater than the perceived risk of an ERP implementation. Correspondingly, your IT department has a difficult time recruiting top young talent, since keeping COBOL programs patched together is not viewed as being on the cutting edge of technology coolness.
If your financial auditors are becoming more and more openly critical in their reports to your Board of Directors, you may be approaching ERP readiness. Auditors are growing less tolerant of antiquated manual financial controls and gaps in control, knowing that world class financial controls, responsible segregation of duties, and automated exception reporting is all a normal by-product of an ERP system.
Lastly, if there is a general feeling that it is time to standardize the company around common processes and controls, you may be getting ready for ERP. This feeling can be driven by wanting to align and focus the company around strategic objectives, or it may just be that some major housecleaning is badly needed as a long term result of acquisitions, legacy customizations, and regional initiatives.
To be very literal, no company is every truly “ready” for ERP – even on go-live. The nuance of “ready” in this context is “recognize the need for”, and the needs should be pretty big and pretty identifiable. There is nothing subtle about an ERP implementation; for that reason, there should be nothing subtle about your company’s need for ERP. Bottom line, if you’re not sure you are ready for ERP, you probably aren’t.
Your guide to using vendor demos to make an informed ERP selection decisionDownload
A comprehensive guide to help you identify requirements for your ERP selectionDownload
Expert advice to help you achieve approval and funding for your ERP projectDownload
What you should be looking for in an agriculture ERP to ensure it meets your farming business needs
How your ERP can reduce business costs, and which of these you should focus on when selling ERP t...
Essential compliance features that your public ERP must have - don't risk the consequences of neg...