Three Habits That Quietly Sabotage Your System (and the Owners Who Have Them)

Here is something we have learned the hard way, across a lot of implementations: a system ends up mirroring the company that runs it. If the business has good habits, the system makes them faster. If it has bad ones, the system inherits them, and then magnifies them.

So when an ERP project disappoints, the cause is usually not the software. It is a habit at the top that quietly shaped every decision. We see three again and again. None of them are about technology. All of them are about how the people in charge behave.

Habit 1: "I Approve Everything"

This one starts as a virtue. The owner cares, the owner is careful, the owner wants to know what is going on. Fair enough. But left unchecked it becomes a habit where every small action in every department somehow ends up needing approval from the top.

We once saw a company of more than 200 people where a RM 50 lunch receipt, a claim for entertaining a customer, still needed the boss's personal sign-off. There was no rule anywhere that said small, routine things could simply flow. So everything queued at one desk.

In the system, this habit shows up as a wall of approval steps. The boss becomes the bottleneck. Work stalls while people wait for a signature on something that never needed one. And then, quietly, staff start doing the work off-system just to get moving, which defeats the entire point of having a system at all.

The fix is to make trust a setting. Good software lets you say "small and routine flows automatically, big and unusual escalates to me." A RM 50 claim auto-approves or goes to a line manager. A RM 50,000 purchase comes to you. Set thresholds, delegate the rest, and spend your attention on the decisions that actually move money or carry risk. You do not loosen control by doing this. You aim it.

Habit 2: "I Want Whatever I Saw on LinkedIn"

The trend-chaser means well too. They are curious, they want the business to be modern, they do not want to be left behind. The trouble is that every shiny thing they scroll past becomes a new requirement.

Install the latest automation bot. No, build our own platform. With AI. That handles every case we can imagine. We have watched a business pour serious money into a bespoke platform to do what an off-the-shelf system like Odoo already did about 90% of, out of the box. The budget kept growing on the promise of "just one more fix and it will be perfect." And the people who would actually live in the tool all day, the ones best placed to say what it needed, were never asked.

In the system, this habit shows up as something over-engineered, never quite finished, expensive, and quietly unused. It looks impressive on a slide and gets ignored on the floor.

The fix is to start from the pain, not the trend. Pick the real problem that is costing you real money, and solve that. Ask the end users what would make their day easier, because they know. Buy the 90% that already exists and build only the 10% that is genuinely your competitive edge. "Just make it work, we know what we want" is one of the most expensive sentences in any project, precisely because it skips the people who know what "work" actually means.

Habit 3: "Just Replicate Exactly How We Do It Now"

This one sounds safe, which is what makes it dangerous. The instinct is to keep everything familiar, so the team is asked to rebuild today's process in the new system, step for step, inefficiencies and all. Nobody stops to ask why a particular step exists.

So you pave the cow paths. The double data entry gets rebuilt. The three approvals that could have been one get rebuilt. The report nobody reads gets rebuilt. You end up with a shiny new tool that runs your old problems faster than ever.

And the process improvement, which is the single most valuable part of the whole exercise, never happens. We have made this point about why implementations fail, and it is worth saying again here: the software is just the tool. The cleaning-up that should come with it is where the real return lives.

The fix is to treat the implementation as a chance to tidy up. Keep the parts of how you work that are genuinely how you win. Let go of the habits that were never strategy, just history. A good consultant maps how work flows today, points at the snags, and designs something cleaner that the system then quietly enforces.

The Common Thread

Notice that none of these three are software problems. They are leadership habits. The bottleneck, the trend-chasing, the refusal to question the old way, all of them live in the company long before any system arrives.

That is the uncomfortable, and freeing, truth. The technology is ready either way. It will faithfully mirror a business that hoards approvals, chases shiny objects, and never improves. Or it will mirror one that delegates sensibly, solves real problems, and is willing to get better. Same software, very different outcome.

So before you choose a platform, it is worth a quiet look in the mirror. Which company is yours about to reflect?

If you would rather have someone walk your processes with you and flag the habits worth breaking before they get baked into a system, that is exactly what our process is built to do.