Q.3 Imagine that in the ERP implementation you are involved with, users that are reluctant to get involved with phase 2. What issues, problems and risks, both short and long term, does this present?
Phase 2 is where ideas and theories are transformed practices and results it is time to plan in detail how the package is going to work for the company. Where the system is tested to see if it gives the desired results, to determine how effective the system is. If there are any problems or unforeseen results arise from the test, in this phase solutions must be developed. Having the many different users involved in the step helps implementation process greatly and the long term
Reluctance by users is not uncommon in implementation on a new system but can be damaging to a successful implementation as it creates problems between users who feel that the others aren’t being helpful or supportive to the project. Users experience and suggestion which could have been useful to the project will go unheard if they do not participate in phase 2.
Users who show reluctance in understanding system may also be less than enthusiastic in learning about the system and how it works, meaning that forms of training or information seminars could be wasted on them and lead to more problems down the tracks as the user has resisted getting to know the system.
With these problems caused by the reluctance of some users, valuable knowledge is not shared between users for, resistance to learning how to make use of the system could delay work goals and cost the business money and place more undue pressure on the other users of the system. While there is no easy way of getting all users to see that getting involved with the system from the beginning is best for all concerned, management should do all it can to try and convince or encourage users to try and help out where possible and not be discourage by change, or else the business could lose out big time.
