Insights
ERP and what you should not do after installing the system
blog
Installing an Enterprise Resource Planning (ERP) system is a major investment for an organisation, aimed at improving work efficiency and integrating data across every part of the business into one. However, a successful installation is only the first step. The post-implementation period is the most critical juncture, deciding whether the organisation will be able to use the ERP system’s potential to the full.
Here are the things an organisation should absolutely not do after finishing an ERP installation:
1. Do not neglect change management
Installing an ERP is not just swapping software — it changes how people in the organisation work.
- Don’t assume everyone will adapt on their own: Don’t assume staff will understand and accept the new processes immediately without support. Resistance to change almost always occurs after installing a new system.
- What you should do: Provide continuous training, not just a single session when installation finishes, and create “champions” in each department to help transfer knowledge and encourage real adoption within their teams.
2. Do not skip post-installation review and evaluation
An ERP system is not a “install it and you’re done” system — it must be reviewed to ensure it delivers the expected results.
- Don’t disband the Core Team: The consultant team and core user team should not dissolve the moment the system goes live; there should be a regular Post-Go-Live Review for at least 3–6 months.
- What you should do: Check the KPIs set before the project started, such as closing time, inventory accuracy, or the order cycle. If the numbers don’t improve toward the targets, you must analyse and immediately improve the processes or system configuration.
3. Do not neglect data quality and cleanliness
An ERP system depends fundamentally on data. If the data entered is incorrect, the results will not be reliable — known as “Garbage In, Garbage Out.”
- Don’t let data become contaminated: Don’t let users enter incomplete or duplicate data, or leave master data unmaintained — such as customer lists, item lists, or the general ledger.
- What you should do: Appoint data stewards responsible for controlling and regularly checking the quality of master data, and verify the integrity of transaction data each day.
4. Do not stop improving and updating the system
The business world changes fast, and ERP technology is continuously developed.
- Don’t use the old version forever: Don’t be afraid to upgrade the system, or to install patches and bug fixes — because using an old software version means the organisation misses out on new features, security, and performance improvements.
- What you should do: Plan system updates as part of the annual budget, and keep studying the new functions the vendor has added in order to apply them to your changing business processes.
5. Do not leave users to solve problems alone
When there is a problem or a usage question after installation, staff need a point of support they can rely on.
- Don’t have no support channel: Don’t leave the organisation without a clear support function, or leave each user to find their own ad-hoc fixes — which can lead to mistakes or off-system “workarounds” that cause data integration to fail.
- What you should do: Set up a technical support team (Help Desk) or a team of super users to receive and resolve usage problems at first level, and provide a channel to contact the consultant team or vendor for complex issues.
Conclusion
The ERP system is a powerful tool, but that power is only realised when the organisation prioritises continuous, disciplined use after installation. Avoiding these “things you should not do” will help the organisation achieve its return on investment (ROI) and drive the business toward sustainable growth.