6 things you need to consider before you begin your ERP implementation: Part 2
If you haven’t read part one of this blog please click the link to get caught up!
If checklist one through three gets a check mark, you’re on the right track to avoiding as little problems as possible. Number four on the list is something that you must be responsible for because, you can’t blame all ERP implementation failures on your partner. Sometimes when a partner gets a client and there ready to kick start their plan, the clients give them all their “baggage” to fix and then leave. They eventually come back at the end, near the go-live date and say things like “Are we ready to go live yet?” Have you tested the system? Nope. Has your staff gotten trained? Nope. Then the answer to your question is nope. You don’t want to be that kind of client. Therefore make sure the implementation goes in steps or phases and make sure to have regular follow ups on the progress that has taken place.
Be motivated! Sometimes implementations take a while to finish, you might be checking off each suggestion on the list but when you come to number five you realize that what’s your lacking in. You need to be upbeat about this whole process, I’m not saying jump up and down and scream for joy that you are getting new accounting software. But at least have a good attitude towards the implementation; I say this because getting something new isn’t always a good thing. You have to retrain your staff; get familiarized with a new system and implement it to your company. That can be a bothersome to someone resulting in them giving you a hard time. As the client, be positive and have a good outlook on this new system, which could ultimately better your performance in the long run.
Last but not least number six on the checklist is to plan for everything and anything that could happen. Once one to five is checked off, be aware of number six. Even though you have everything planned to a T anything could happen from employees’ issues to company changes. Just be prepared for whatever can happen because even though you might be well prepared when it comes to the implementation there’s always a chance of a problem that could occur. You can’t predict and prevent everything but give yourself a fighting chance if a problem arises.
By: Natalie Williams, Marketing Coordinator, WebSan Solutions Inc., a Canadian Certified Microsoft Dynamics Partner