A business can spend months choosing a new system without asking what it is willing to stop doing.
There will be meetings about features. Demonstrations. Discussions about cost, training, and timelines.
But somewhere in those conversations, someone will say:
“We need the new system to work exactly like this.”
That is the moment worth paying attention to.
Because “exactly like this” may include the approval everyone waits for, the report nobody reads, and the spreadsheet only one person understands.
What, then, are we asking the new system to improve?
Consider a familiar situation.
A routine decision sits on a manager’s desk. The team knows what needs to happen. The customer is waiting. But the person who must approve it is unavailable.
When the decision finally comes through, everyone gets back to work.
The delay becomes another ordinary part of the week.
Now imagine that same situation inside an ERP system. The request arrives instantly. The manager receives a notification. Everyone can see that it is pending.
The waiting has become more visible. Who has decided whether it is still necessary?
That question can lead somewhere uncomfortable.
Perhaps the approval protects the business from a real risk. Perhaps the team lacks the information to decide safely. Perhaps the manager has never been asked to let someone else make the decision.
Each answer leads to a different conversation. Buying software does not spare us from having it.
When a business begins implementing Odoo, the invitation to rethink how work happens is already there. Every familiar process has to be explained to someone who may ask a question nobody inside the business has asked for years.
“Why?”
Why does this need your signature?
Why is this information entered again?
Why does the work stop when that colleague is away?
Sometimes there is a good answer. Sometimes the answer begins with the name of someone who left the company five years ago.
How much of the way your business works was designed for a business you no longer are?
A rule introduced when the team was small may still shape decisions long after the team has grown. A check added after one mistake may have become a permanent hurdle. A temporary workaround may now be part of someone’s daily job.
These habits can be difficult to question because people have worked hard to keep them functioning.
The colleague with the spreadsheet may have spent years making sure nothing gets missed. The manager who checks everything may feel personally responsible when something goes wrong.
Ask them what the current process helps them protect. Ask what makes their work harder. Ask what they would change if they believed the answer would be taken seriously.
Then be willing to hear something inconvenient.
A leader might discover that their own approval is causing the delay. A department might have to share information it has always kept to itself. A project team might learn that the proposed new way overlooks something essential.
The willingness to question has to apply to everyone, including the people introducing the system.
Before the next implementation meeting, try asking:
“If this process did not already exist, would we choose to introduce it today?”
Give people time to answer. Let them disagree. Ask for examples.
You may decide to keep the process. You may decide it needs to change. Either way, you will have a reason stronger than familiarity.
A new system creates an opportunity to make those choices deliberately.
What is one process in your business that people have learned to work around—and stopped believing they can change?