Moving to an ERP is first and foremost an organizational change project, in which technology serves as a tool. If you fail to prepare the company for new processes, employees for a new logic of work, and managers for new transparency, even the most expensive system will fail.
Successful implementation is possible, but only by consistently working through four key stages of organizational change. Below is how to navigate each of them so that the system comes to life and the business keeps running.
An ERP doesn't solve problems automatically - it only amplifies what already exists in the company. That's why order in processes and data matters more than the choice of vendor.
Organizational change is the key to success: 4 stages
Implementation is not installing software, but reshaping how the company works with data, roles, and accountability. It's helpful to think of the project as four sequential stages: from a readiness assessment to continuous development after go-live.
Stage 1: Diagnostics and business readiness
Before choosing a system, answer the question: "Why do we need an ERP?". Having a clear goal determines the success of the entire project. ERP implementation leads to changes in business processes, and you need to be sure the business is ready for it.
- Pre-project research. Collecting and analyzing all the business processes that the new system will cover.
- Assessing the current maturity of processes. An ERP doesn't solve problems automatically - it only amplifies what already exists in the company.
- Data audit. Unstructured, duplicated, or contradictory data is one of the main killers of ERP projects.
Stage 2: Process design and system configuration
At this stage, the future business processes and system configuration are defined:
- Designing the governance model. Building a single data perimeter and properly distributing roles across corporate systems.
- Choosing an implementation methodology. ERP projects are traditionally built on the waterfall model - most often such a project has a clear business request and a predictable scope of work.
- Developing detailed requirements. Vague requirements are one of the main causes of failure. If you want to implement an ERP with minimal risk, start with diagnostics.
- Forming the project team. Training the client's project team is a key stage - without a sufficient level of knowledge, the team will be unable to interact effectively with implementers or properly adapt its processes to the system.
Vague requirements are one of the main causes of project failure. The more uncertainty in the requirements, the higher the final budget and timeline. Start with diagnostics, not with buying licenses.
Stage 3: Working with people and resistance
The most underrated stage. The statistics are unforgiving: implementation affects the positions of employees and managers, places new demands on their skills, knowledge, and competencies, and redistributes authority and responsibility.
- Communication campaign. Employees must understand why processes are changing and what benefit they will gain.
- Training program. There's no way around training the client's project team - a lack of knowledge leads to resistance and sabotage.
- Managing resistance. A typical case: after a new ERP release, employees collectively sabotage its use, preferring the old processes in Excel. This risk needs to be addressed before the start, not after the system is delivered.
A typical case: after a new ERP release, employees collectively sabotage its use, preferring the old processes in Excel.- Implementation practice
Stage 4: Go-live and continuous development
ERP implementation is not the finish line, but the moment when the company first gains a coherent digital architecture.
- Pilot launch. Launching in a limited part of the business to surface hidden problems before scaling.
- Scaling. Gradually connecting new departments, business functions, and branches.
- Post-project support. A modern ERP requires support, regular enhancements, and attention to data. This is a normal lifecycle, not a sign of a failed implementation.
Project goal, pre-project research, process maturity assessment, data audit.
Governance model, choice of methodology (usually waterfall), detailed requirements, project team training.
Communication campaign, training program, managing resistance before the start.
Pilot in a limited area, scaling to departments and branches, post-project support.
Where projects break: a map of the main risks
Most ERP failures are not about technology, but about preparation. Below is exactly where the risks concentrate by stage and what to counter them with.
| Stage | Main risk | How it's covered |
|---|---|---|
| Diagnostics | No clear goal, dirty and duplicated data | Pre-project research, data audit, maturity assessment |
| Design | Vague requirements, unprepared client team | Detailed requirements, single data perimeter, team training |
| People | Sabotage, reverting to Excel, loss of competencies | Communication, training, working with resistance before the start |
| Go-live | Schedule and budget overruns, problems when scaling | Pilot in a limited area, post-project support |
Practical recommendations for change management
- Set up a single change committee that will control all system modifications, planning the work so as to minimize the risk of disrupting business processes.
- Engage an integrator with experience in your industry. The maturity level of your IT partner and their expertise in your sector are critically important factors.
- Be realistic about timelines and budget. Failure rates are no better than the global averages anywhere.
In addition to the cost of licenses and implementation, the budget should include staff training, customizations for unique processes, support in the first year after go-live, and a temporary slowdown in work during the adaptation period.
Professional help with ERP implementation: G-Invest expertise
G-Invest is a consulting firm specializing in legal and financial advisory, building effective corporate structures, and advisory support on matters of conducting commercial activity. For a consultation on change management during ERP implementation, contact G-Invest.
Frequently asked questions
How do you assess a company's readiness for ERP implementation?
Use a checklist of three blocks: business process maturity (how standardized they are), data quality (whether there are duplicates and chaos), and team readiness (whether there are internal change leaders).
What should you do if employees sabotage the new ERP system?
Sabotage is almost always a consequence of insufficient communication and training. You need to return to the people-focused stage: hold one-on-one meetings, strengthen training, and involve informal leaders in the enhancement process.
What hidden costs arise during ERP implementation?
In addition to the cost of licenses and implementation, budget for: staff training, customizations for unique processes, support in the first year after go-live, and a slowdown in work during the adaptation period.
Implementing an ERP - start with change management
G-Invest will help you assess business readiness, bring order to processes and data, and build change management so that the system comes to life and the team embraces it.