ERP project management means juggling a lot of different things; and while system selection, data migration, and the many other processes involved are undoubtedly important, communication is absolutely essential to get a project completed on time, and on budget. There is a lot of information to relay to a lot of different people during an ERP implementation, make sure you and your team are not making some of these fatal errors that could potentially torpedo the entire project.
For successful ERP project management, make sure your communication plan does NOT look like this:
The project manager is getting too much information.
Your project manager will have many tasks to do and can easily become overwhelmed if he/she is the sole person in charge of communicating with the team and that communication could easily get lost amongst other tasks or misinterpreted. While the project manager should be well informed about what’s going on, direct communication between various team members is important as well, especially those directly impacted by the communication.
The project manager is not getting enough information.
On the other side of what we described above, your project manager may not be getting enough information. While direct communication between team members and levels is important, the project manager cannot be left in the dark and needs to know who is working on what and where they are in the process. That way progress is being monitored and goals are being met; two vital parts of a successful ERP project.
The lines of communication get crossed and are never uncrossed.
With so many people and so much information flying around, it’s easy for the lines of communication get tangled up somewhere. When this happens team members begin heading in a different direction than she should be which can not only waste time but damage the project. We’re all human, so there is no way to completely eliminate confusion, which is why continual communication is critical to identifying these situations early on and correcting them before too much time or money is wasted.
Information is not centrally located.
Whether you have team members working on this ERP project all in one office or spread out over a few different locations, they will need to access project documents from various locations and devices. If they cannot quickly and easily access what they need their productivity can drop which may in turn extend the time frame for the project. According to a number of studies on the subject, knowledge workers spend up to %40 of their time looking for information and are not guaranteed to find it! Make sure your team does not have this issue by storing all ERP project related documents in one place and the entire team knows where to find them and how to organize any documents they add in a way that make sense for everyone.
Project documents are not being updated.
As you work through your project things are going to change, is your team keeping the necessary documents up to date? If they are not there is an increasingly large risk that mistakes will be made since tasks will be carried out based on outdated information. This is the type of thing that could lead to complete project failure.
Being in charge of ERP project management,even being a part of the ERP project team is not easy, and it’s a task made much harder when communication is a problem. Make sure to stay clear from the above mistakes and your ERP implementation, while it may not be completely free of hold-ups, is sure to be signifciantly smoother when everyone is communicating clearly and consistently.
Pick up more tips of what not to do during an ERP implemenation in the white paper below!