Why Your Team Still Relies on Spreadsheets Instead of Your System

Here’s a question worth sitting with: if your ERP is working, why does your operations team still run a parallel spreadsheet? Not because they haven’t been trained. Not because they don’t know the system exists. Because at some point, they learned it wasn’t reliable enough to bet a decision on.

That’s the manual override problem, and it’s more expensive than most COOs have stopped to calculate.

The spreadsheet didn’t win. The system lost.

Shadow systems don’t appear because people prefer complexity. They appear because the system of record has let someone down enough times that they stopped trusting it.

A buyer gets burned by stock data that was two days old. A planner makes a call based on ERP demand signals that didn’t account for a last-minute sales order. A warehouse manager discovers the system shows 400 units available, and the shelf shows 280.

Each time that happens, someone builds a workaround. A running spreadsheet here. A WhatsApp confirmation there. A manual recount before every major decision. Over time, the workaround becomes the process, and the ERP becomes the system you update after you’ve already figured out what’s happening.

What it actually costs

The obvious cost is errors. A formula breaks, a row gets deleted, two versions of the same file circulate simultaneously, and a decision gets made on the wrong number.

However, the less obvious cost is speed. Every decision that runs through a manually maintained spreadsheet carries a lag: the time it takes someone to update it, reconcile it, share it, and wait for the relevant person to act on it. In procurement and inventory, that lag compounds fast.

Let’s take the hypothetical example of a mid-sized distributor running purchasing decisions off a spreadsheet that gets updated every Monday morning. A demand spike happens on Wednesday. By the time it shows up in the reorder calculation, it’s the following week. The response is already five to seven days behind the event. Multiply that across a product catalogue of 800 SKUs, and the cumulative cost of emergency orders, missed windows, and overstock from over-correcting is no rounding error.

There’s a third cost that rarely gets named: the cost of the person maintaining the spreadsheet. Someone senior enough to understand the data is spending hours every week on a job that should be automated. That’s decision-making capacity being consumed by data housekeeping. Don’t underestimate the little things that ERP data integration can solve.

Why does the behaviour persist even when better tools exist

This is the part that matters most: manual overrides don’t disappear when you implement a new system. They persist until the new system earns enough trust to replace the old habit.

That trust has a specific definition in operations: the system tells me what I need to know, when I need to know it, without me having to verify it elsewhere.

Most ERP implementations don’t clear that bar on day one, or even year one. Data is inconsistent. Integrations are partial. Reports require interpretation. So the spreadsheet stays, running alongside the system, as a hedge against being wrong.

The organizations that successfully retire the spreadsheet don’t do it by mandate. They do it by making the system more trustworthy than the workaround: faster, more accurate, and specific enough to the decision at hand that checking elsewhere feels like extra work rather than due diligence.

The question to ask your operations team

Not “are you using spreadsheets?” The answer is yes, and defending it is a distraction.

The right question is: what would have to be true about your system for you to stop?

The answers will tell you exactly where your data trust deficit lives, and what it would take to close it. That’s a more useful starting point than another system rollout that lands alongside the spreadsheet instead of replacing it.

Key takeaways