Organizations opt for an ERP to improve the efficiency of their business processes. Non-aligned systems, legacy software, and manual processes have made a way to the modern-day ERP that beautifully streamlines processes and data and makes decision making simpler.
However, the game is not over with the implementation bit. The real work and challenge appear post-implementation. That one year after you ‘go-live’ with your ERP implementation is the most crucial one, as it determines the long term success of the system. The challenge is that many organizations don’t realize meaningful business process improvements after their ERP implementations.
The real return on investment from the ERP comes from the post-implementation activities that occur within the first year. Post-implementation activities need to be meticulously planned and executed for the ERP to perform at its top form. Performing a post-implementation review, determining the governance strategy, continued training, and other activities ensure the on-going success of the ERP solution.
You should plan your post-implementation activities around the time you are running your User Agreement Testing (UAT). The plan should address the People, Processes, and Technology of the operational ERP software.
The core team that has worked on the go-live of the ERP implantation should sit down and discuss what was successful about the implementation, what did we learn from the project, and what would you change going forward. The team must document theses “wins”, “learns”, and “changes”. Writing down these discussion points will help you with future projects.
It is important to have periodic training of the users to help them navigate through the ERP system.
As much as training is important, it is equally important to document the new process. When after a few years when the members of the core team move to some other department or leave the company, there is no arbitrary knowledge gap in the system. Decisions are executed without understanding the initial considerations of why the system was set up the way it was. Documenting the processes and significant decisions will help extend the life of the ERP solution. Yes, the system will evolve, but as you grow the system, you should create a written knowledge of the how and why considerations. Future decision-makers will be more informed and will have an understanding of the original vision for the system.
A post-implementation review is very important to ensure that the setup for the system matches with the end-users expectations and that there are no bottlenecks for the users to get their work done.
ERP systems need care and feeding Updates need to be scheduled and deployed appropriately, without significant user interruption. Communicating about the new releases along with the features that it brings, is very important. One needs to be mindful if adequate training is necessary with the new updates.