In brief
An ERP project acts as a revealer of how a company really works. It highlights tensions, inconsistencies and grey areas that existed well before the software arrived, but that people had learned to work around, ignore or "tinker" with.
Five revelations come up almost every time : blurred roles and responsibilities, inherited processes that are never questioned, rigid functional silos, a gap between leadership's vision and field reality, and a digitalisation that is more cosmetic than structural.
It is not a problem, it is an opportunity. An organisation that accepts this mirror, even if it is uncomfortable, gains a formidable lever for improvement.
An ERP, just a tool ? Not quite
When a company decides to equip itself with an ERP, it often thinks it is starting a technology project : choosing a solution, defining a scope, migrating data, training users.
And that is true. An ERP is indeed a tool.
But what we often forget to say, or discover a bit too late, is that an ERP project also acts as a revealer of internal functioning. It highlights tensions, inconsistencies and grey areas that existed well before the software arrived, but that we had learned to work around, ignore or "tinker" with.
In our line of work, this tipping point is almost systematic. The company thinks it is digitalising a process. What it discovers is that it must first redefine itself.
The five revelations an ERP triggers
At Niboo, we have identified recurring patterns. They are not "mistakes" strictly speaking, but revealers. Signals that an organisation runs on instinct, without always having formalised its internal logic. And that the ERP, by seeking to structure things... disturbs this implicit balance.
1. Blurred roles and responsibilities
An ERP relies on a logic of flows : each piece of data passes from hand to hand, from department to department. But what happens when nobody knows precisely "who does what" ? When tasks overlap, or when people have been "sorting it out between colleagues" for years ? The software cannot improvise. It brings this blur to light, sometimes brutally.
What an ERP reveals is not always pleasant. But it is healthy.
We often expect the ERP to simplify, streamline and improve. And that is true, in the long run. But to get there, you sometimes have to go through a phase of exposure. And it is precisely this phase that good projects know how to anticipate and support.
An ERP, well thought out and well supported, does not impose another way of working on you. It invites you to clarify what you are already doing, to align your teams, to make your company more legible... for your customers, your employees, and yourself.
It is not a miracle tool. But it is, often, the start of a turn.
Frequently asked questions ?
2. Inherited processes, never questioned
"We've always done it this way." A phrase we hear often... until the system can no longer take it. The ERP forces you to describe, formulate, structure. And in doing so, it reveals how shaky, bypassed or simply obsolete some processes have become.
3. Rigid functional silos
In some organisations, each department has its own way of working, its own tools, its own logic. As long as everyone stays in their own corridor, it "works". But the ERP, by definition, crosses silos. It demands cross-functional consistency. And when there is none, friction appears quickly.
4. A gap between leadership's vision and field reality
Decision-makers may have a very clear idea of what they want... without realising how far the teams are from that vision. The ERP, by revealing real usage, undocumented habits and resistance, brings this gap into the open. And it is sometimes a shock.
5. A digitalisation that is more cosmetic than structural
Many companies think they are digitalised because they use tools like Teams, Drive or a standalone CRM. But in practice, very few processes are truly automated, little data is cross-referenced, and information governance remains unclear. The ERP ends this illusion. It is no longer about having tools : it is about making them work together.
It's not a problem. It's an opportunity
At this point, you might think the ERP only adds complications. But that would be a misreading.
What the tool brings to light are not weaknesses created by the project: they are realities that were already there, but until now invisible, or deliberately ignored. In this sense, the ERP plays the role of a mirror: it does not judge, but it shows.
And that is where everything is decided. An organisation that refuses to see these tensions will tend to postpone, to complicate, to look for "solutions without change". It is the perfect breeding ground for a failed project.
But an organisation that accepts this mirror, even if it is uncomfortable, has a formidable lever for improvement. What was meant to be a technical project then becomes a strategic project.
It acts as a revealer of internal functioning. Five revelations come up almost every time: blurred roles and responsibilities, inherited processes never questioned, rigid functional silos, a gap between leadership's vision and field reality, and a digitalisation that is more cosmetic than structural.
No. What the tool brings to light are not weaknesses created by the project : they are realities that were already there, but until now invisible or deliberately ignored. The ERP plays the role of a mirror: it does not judge, but it shows.
It is the phase where the ERP is installed, configured and deployed in your company. It is distinct from adoption, the moment when your teams really use the tool, day to day.
An organisation that refuses to see the tensions the ERP reveals will tend to postpone, to complicate, to look for "solutions without change". It is the perfect breeding ground for a failed project.
Not necessarily. Many companies think they are digitalised because they use such tools, but very few processes are truly automated, little data is cross-referenced and information governance remains unclear. The ERP is about making tools work together.
An ERP that is well thought out and well supported does not impose another way of working. It invites you to clarify what you are already doing, to align your teams and to make your company more legible for your customers, your employees and yourself.
Conclusion : an ERP does not create tensions. It reveals them
And in this revelation, there is an immense opportunity: that of making your organisation healthier, more robust, more fluid. You just have to be ready to face it.
An ERP is a tool. But it is also a moment. A moment of truth. And at Niboo, we make sure it is a constructive one.
Feel free to check out our latest updates on our social media channels :
You do not have Odoo :
Let us start the journey together !
From analysis to implementation, we build an Odoo that truly fits your needs.
. 