Skip to Content
ERP ImplementationProject Management
Mark Scheffel Mark Scheffel Published Updated 6 min read

The three biggest project risks

Summarize this article with AI

Want to quickly get to the core and key insights? Open this article in your favorite AI tool.


An ERP implementation often starts with the same question: what risks could hinder the success of this project?

As an implementation partner of Odoo, we have been doing implementations of various sizes and complexities for many years. In practice, we see the same project risks recurring.

An ERP implementation is not just about software. The biggest risks often arise within the organization itself: employees are insufficiently involved, the scope grows during the project, and tasks are not validated on time.

Employee engagement

Implementing a ERP system is often not the choice of the employees who have to work with it.

They are used to the current package. They know the daily tasks and have often found their own workarounds to get their work done.

A new system can therefore create uncertainty. Employees wonder what will change and whether they will still be able to work as well.

Therefore, involvement begins with a clear vision from the management. There is a reason to choose new software. It is important that the management explains why that choice was made and how the new system supports the future of the company.

Anyone who wants to involve employees in an ERP implementation should not wait until the training. Involve key users during the package selection and ask for their input on important decisions.

Also highlight the strengths of the current package. This information helps to better align with what employees find important during the setup and training.

Resistance often arises from uncertainty. Someone may perform their job well today and suddenly have to work with software that is still unfamiliar.

It is not wise to completely rebuild the old system. Employees need to learn to work with the new software and understand why certain processes are changing.

That is why we pay a lot of attention to training and transfer. In our approach, we use the train-the-trainer principle, among other things. This way, there is someone within the organization who can provide first-line support to colleagues.

If a key user can explain a process to a colleague, we also know that the knowledge has been well transferred. It is wise to start early with work instructions that are written by and for employees.

An acceptance test, support during the go-live, and guidance after the go-live help employees to start with confidence. Those who inform employees only at the last moment make the transition unnecessarily difficult.

2. Scope and customization

Before the start of an implementation, we try to provide a realistic budget. That budget is based on the discussions and choices that have been made beforehand.

During the project, new wishes almost always arise. Evolving insights and feedback from employees can lead to changing requirements.

That is not inherently wrong. The risk arises when every new wish is directly added to the project.

By accommodating all wishes, you quickly encounter budget overruns. That does not automatically mean you will get a better system.

Therefore, we prefer to start with the smallest possible implementation. We stay close to the standard and first set up the applications that generate revenue for your company.

We do not simply go along with every wish. First, we want to understand why a modification is necessary and what problem it solves.

By first learning to work with the new package as intended, future wishes become more visible. This prevents you from rebuilding the old package.

We also try to minimize customization. This makes the system cheaper and more manageable. It becomes easier to train employees and to use a future version of Odoo.

In our experience, after three to six months of working with the system, at least 50% of the customizations made are found to be unnecessary. Therefore, we advise giving the standard a good chance first.

You can read more about this consideration in our blog about the pros and cons of customization.

Custom solutions can certainly be the right answer. But it must be clear why standard Odoo or another method does not sufficiently align. The question is not only whether something is technically possible, but also what it costs to maintain, test, and support the solution over the years.

3. Validate project tasks

When we start a project, we create a project plan based on the quote. That plan forms the basis for the implementation.

The project plan provides insight into progress, clarifies what work is still outstanding, and helps to monitor the budget. It is also an important communication tool between the client and the implementation partner.

A project task is only completed when the client has validated and approved the result. The consultant's work may be finished, but that does not automatically mean the task has been delivered.

This is where a significant risk arises in practice. When someone approves a result, that person also takes responsibility for that choice.

That can be quite nerve-wracking. Employees may therefore postpone the validation of tasks. This creates a long list of outstanding tasks, with no clear indication of how much work is still involved.

To prevent this, we place a lot of emphasis on validation during the project. Sometimes we conduct tests together with the relevant employee. When validation is delayed, it must be escalated.

The members of the project team must have sufficient knowledge to test the processes. They must also have enough mandate to make decisions and give approval.

A good project leader at the client is also important. This person guides the implementation internally and motivates project members to test and validate.

The project leader must also have sufficient mandate to request action when tasks are left undone. This person is the central point of contact, or the SPOC: the single point of contact.

In our Odoo project approach we therefore establish in advance who decides, who tests, and who is responsible for validation. This way, the project does not solely rest with the implementation partner.

Limit project risks before they become problems

The three biggest project risks are easily recognizable:

  • insufficient involvement of employees;

  • a scope that keeps growing with wishes and customizations;

  • project tasks that are not tested and validated on time.

By taking this into account in advance, an ERP implementation has a much better chance of success.

Ensure a clear vision from management. Involve key users and employees in time. Start with a manageable scope and give the standard a fair chance first.

Also clarify who is responsible for testing, decisions, and approval. An experienced implementation partner can help make these risks visible, but the project remains a shared responsibility.

An ERP implementation is only successful when not only the software is set up, but employees can work with it and the organization has validated the result.

Plan an ERP implementation without surprises

Do you want visibility in advance on the main risks, choices, and responsibilities within your ERP project? Check our Odoo project approach or contact us for a practical conversation.

Read more about this topic

ERP Implementation Project Management

Share this article