Three considerations you might have left out of your ERP implementation plan
Robert Burns said in 1785
The best laid schemes of Mice and Men go aft awry, And leave us nothing but grief and pain, For promised joy!
After more than 230 years, the same thing can happen with an ERP implementation. That one element in your plan can lead you to grief and pain.
1. People have day jobs
Most of the people on your implementation team still sit at their old desk and have many of the same responsibilities as last week. Any ERP implementation is hard work and takes time and commitment. When faced with a choice between writing one more purchase order or finishing the journal entry for monthly depreciation instead of studying an ERP document, you know most people will stick with what they are familiar with.
A successful implementation plan requires commitment from the whole enterprise. The boss of that buyer needs to say ‘no, work on ERP and I’ll have someone else write that purchase order’. The accounting manager might consider hiring a temporary replacement for journal entries. The executive sponsor and the whole team has to have the organizational commitment.
2. Your team will make unnecessary assumptions
ERP implementation plans demand a lot of coordination. The whole team (including the project manager) should avoid making assumptions. Test every transaction. Make changes as needed and test again. When one group proves their process works, be sure the groups before and after test the process again. Assuming that it works on one place and probably will work everywhere is a sure path to pain. Even more importantly never assume that whatever the ERP salesperson said is true.
3. Restructuring plans
Many return on investment analyses depend on reduced cost to provide some of the return. Is that how you justified your ERP? There is nothing wrong with that justification. If, however, your ERP will achieve this by making people redundant, part of your implementation plan should cover the actual reduction in force. Leaving this out of your plan will lead to confusion and bad feeling, and can also ensure your implementation does not meet its ROI goal. Months earlier you might have found a different way to achieve your needed return.
An ERP implementation requires a balance of resources and requirements. Too much reliance on consultants can be as much a problem as too much reliance on doing the job in house. Be sure too that you understand how all the features in the ERP work and determine if they can benefit your business.
Featured white papers
ERP Implementation: 9 steps to success
The 9 proven steps you should follow when implementing ERPDownload
ERP Implementation Checklist
Over 120 actionable steps to implementing a new ERP successfullyDownload
Manufacturing ERP Implementation Checklist
Over 70 actionable steps to rolling out new manufacturing ERP softwareDownload
9 hidden ERP costs that can blow your implementation budget
Discover critical cost areas of your ERP project that can wreck your budget
Three improvements to expect after retail ERP implementation
The benefits you could see after a successful retail ERP implementation
Risk management and ERP implementation: three tips
Actionable advice for managing risk during an ERP implementation project.