Shadow Spreadsheets: The Sign Your ERP Rollout Didn't Finish
The spreadsheet nobody officially approved is often more trusted than the ERP itself. Here's why that happens, and how to tell a training gap from a real integration problem.
Ask a scheduler which system actually runs production, the ERP or the spreadsheet on the shared drive, and the honest answer is usually the spreadsheet. Nobody planned it that way. It just became the thing everyone trusts because it answers the question the ERP screen doesn't.
Why the spreadsheet shows up in the first place
Nobody builds a shadow spreadsheet to undermine the ERP. It usually shows up because it fills a specific, unglamorous gap that the system rollout never closed.
- The ERP doesn't have a field or report for something the team actually needs day to day, like a customer-specific priority rule.
- The standard ERP report is too slow or too rigid to answer a quick question, so someone builds a faster version next to it.
- Training on a module was incomplete when it went live, so people fell back to what they already knew how to use.
- A workaround that was supposed to be temporary during go-live never got retired once things settled down.
What it costs once it becomes permanent
Once a spreadsheet becomes the real system of record, you end up with two versions of the truth and no clean way to know which one is right. Usually one person understands how it's built and kept current, so the whole process depends on them being around.
Where to look before retiring the spreadsheet
Before telling anyone to stop using it, it's worth understanding exactly what job it's doing.
- Figure out precisely what question or task each shadow spreadsheet answers that the ERP currently doesn't.
- Check how it's kept current, by hand entry, copy and paste, or export, and how often it ends up disagreeing with the ERP's own numbers.
- Identify who maintains it, and what happens to the process if that person is out sick or leaves.
- Ask whether the gap is a missing feature, a missing report, or a habit that never got retrained after go-live.
Where automation helps, and where it doesn't
When it's a configuration gap
If the ERP can actually do what the spreadsheet is doing, and the gap is really about configuration or training that never happened, the fix is closing that gap, not adding another tool. This is usually the cheaper and faster path, even though it feels less exciting than new software.
When it's worth automating
If the spreadsheet is doing real integration work, pulling numbers from systems that genuinely don't talk to each other, that's a fair case for a lightweight sync between those systems instead of a person copying numbers by hand every week. It's still not an AI project, just a smaller, better-defined connection than the manual one it's replacing.
The takeaway
A shadow spreadsheet usually isn't a discipline problem. It's a sign that somewhere in the rollout, a real gap got worked around instead of closed. Worth understanding what job it's actually doing before deciding whether to retire it, replace it, or connect it properly.