18 June 2026
You Bought a System, So Why Is Your Team Still Working the Old Way?
Board meeting, quarterly results presentation. Someone opens the CRM, which should contain 200 leads from the past month. There are 27. The question to the salesperson: where is the rest? The answer comes without hesitation: “I have them in my Excel file. The CRM couldn’t handle it the way we needed.”
Everyone nods. Everyone in the room knows that’s how things work. And no one knows what to do about it.
Buying a system and getting it installed in the company are two completely different things. The licences have been paid for, the training is done, and the implementation is complete. None of that means the system is actually working. The system works when people use it. Every day. Naturally. Without being forced to.
And that’s the trap most companies fall into. If employees avoid using the system, the problem almost never lies with them. It lies with the system, the process, or the implementation. Most often, it’s all three at once.
If you look more closely, most cases come down to three situations. Each one looks different, but they all end the same way: the system sits there while the work happens around it.
A System That Can’t Keep Up With the Work
In most companies where a system fails to gain traction, the problem starts with a simple observation: entering anything into the system takes longer than doing it the old way. A note in an email takes ten seconds. Entering it into the CRM takes two minutes. Under the pressure of a busy day, when the client is waiting and the schedule is falling apart, the system will always lose to email.
Employees aren’t lazy. They’re rational. They choose the path that allows them to get the job done. If the system doesn’t make that easier, they find a workaround. It’s not malicious — it’s simply an economy of time.
The second layer of the same problem is how well the system fits the realities of a specific company. Implementations often follow an “out-of-the-box” approach based on general assumptions, without taking a closer look at how people actually work day to day. A salesperson gets a “negotiation stage” field with five options, even though their industry has twelve. A warehouse worker uses a system that assumes every product has a code, while half of the orders come in with written descriptions. The result: employees use the system only 30% of the time because the rest simply doesn’t fit the way they work.
Workarounds start to appear. A note in an email. A private Excel file. A sticky note on the monitor. Each one exists because someone needed to complete a specific task and the system didn’t help them do it.
A system that slows down work or fails to keep up with real-world workflows won’t be adopted. It will simply be ignored.
Work That Leads Nowhere
It’s a trap that develops slowly and is the hardest one to spot from management’s perspective.
Employees received user instructions. Sometimes they even received training. They know where to click and how to enter the data. But no one explained why it matters. From their perspective, it’s extra work that doesn’t make anything easier. They enter the information into the system and then send the same data to their manager by email because “it’s faster that way.” They don’t see the point, so naturally, they choose the path of least resistance.
The second, even more serious aspect concerns what happens to the data after it is entered. In many companies, information entered into the system simply disappears from the user’s perspective. There’s no report that shows it. No alert when something needs attention. No indication that any of it has actually led to a result. It’s like putting paperwork into a drawer that no one ever opens.
A system that is meant to be adopted has to work both ways. People enter data, and in return, they get something that helps them: a suggestion, a task list, a report, or an alert. A salesperson should know that the CRM will help them stay on top of follow-ups and avoid losing customers. A warehouse worker should know that the system will automatically generate a replenishment list when stock levels drop. An accountant should know that invoices can be issued faster because the data is already in one place.
Without that second side, the logic becomes simple: if no one uses the information, why bother entering it? This is one of the most common reasons why even a well-designed system gradually stops being used. It doesn’t break down overnight. It simply becomes less and less relevant in the eyes of the team.
And this is exactly where it’s worth pausing over one thing. The most common reaction from a business owner to this problem is anger towards the team: “I bought them a system, and they still do things their own way.” It’s a natural reaction, but it leads in the wrong direction. The question worth asking is not “why don’t they want to use the system?” but “what makes it faster and easier to work the old way?” The answer to the second question always leads to a concrete solution. The first only leads to frustration.
Three Systems Instead of One
The last situation is, in a way, the most absurd, because it concerns companies that invested in creating order only to end up with more chaos than before.
A salesperson enters a customer into the CRM. Then they enter the same data into the invoicing system because the CRM isn’t integrated with it. The warehouse receives the order details by email and enters the same information for a third time. The accountant then checks everything in their own separate tool. The system becomes an additional obligation rather than a tool that makes work easier.
At some point, someone says, “Maybe we should just manage it all in one Excel file — at least then everything will be in one place.” And that often works better than an expensive system that doesn’t integrate with the rest of the company’s tools.
The paradox is that the company bought a system to bring order, only to create yet another information silo. Instead of having one consistent view of the business, it now has three different versions of the same reality. And that’s not a problem with the system itself. It’s a problem with a system operating in isolation.
A system that doesn’t integrate with the other tools in the company will eventually be abandoned. Not because it’s a bad system, but because no one has time for doing the same work three times.
How to Fix It
The good news is simple: in most cases, the system a company has invested in can be saved. Replacing it with a new one is less often necessary than it may seem. The first step, however, is not to modify the system, but to observe how people actually work. Where they use the tool, where they bypass it, what workarounds they have created, and why. These are some of the most valuable insights any company has — yet almost no one takes the time to look for them.
Only from that picture can you determine what really needs to be improved. Sometimes it means simplifying the system, removing unnecessary fields, and shortening workflows. Sometimes it means integrating the system with another tool so that data no longer has to be entered in three different places. Other times, it means building an automation that takes over the tasks people find most frustrating. Each of these solutions may require different technology: from simple off-the-shelf integration tools, through custom-designed automation, to extending the system itself with traditional code when the scale or specific needs of the company require it. The key is not to start with the tool, but with the question of what exactly isn’t working.
A system that is a source of frustration today is usually not beyond saving. More often, it turns out to need a few targeted changes to start doing what it was bought to do. The hardest part is when the owner decides to stop fighting the team and starts looking at what is actually getting in the way of their day-to-day work.