The Hidden Cost of Shadow Systems
When the spreadsheet symptom hardens into infrastructure: knowledge loss, duplicate work, version fragmentation, and operational blindness.
A shadow system starts as one person's workaround. It becomes infrastructure the moment other people depend on its output. At that point the institution is running a second, unmanaged system of record — with none of the controls it applies to the first.
Knowledge loss
When the administrator who built the tracker changes roles, the formulas leave with them. The successor inherits a file they did not build, cannot fully validate, and will eventually rebuild from scratch — losing the history in the process.
Duplicate entry
Compliance requires the data in the ERP. Operations require it in the shadow system. The same figures get entered twice, on different schedules, under different assumptions — and drift is guaranteed, not possible.
Version fragmentation
Five trackers for one portfolio means five defensible answers to the same question. None are necessarily wrong; they are simply current as of different moments. Leadership cannot tell which is which without a manual reconciliation.
Operational blindness
The most expensive cost is the question nobody can answer quickly: which awards are at risk right now. If answering that takes an afternoon of reconciliation, the office finds out about problems after they have already happened.
Closing the gap
The remedy is not more discipline around spreadsheets. It is giving the office a shared, live layer that answers the operational questions the ERP was never built to answer — so the shadow system has nothing left to do.
Written by Stowers Scalable Strategies and Analysis, LLC.