Spreadsheets are where almost every reporting culture starts, and for good reason: they are flexible, familiar, and free. The problem is that the qualities that make them great for analysis make them fragile as infrastructure.
The signs you have crossed the line
You do not outgrow spreadsheets when they get big. You outgrow them when they start behaving like systems — without any of the guarantees systems provide.
- The month-end file has a version number in its name.
Final_v7_USE_THIS_ONE.xlsxis not a filename, it is a cry for help. - One person is the pipeline. If reporting stops when a specific analyst is on leave, your infrastructure is a human being.
- Every meeting starts with reconciliation. When sales, finance and operations each bring their own figure for the same metric, the spreadsheet is no longer a source of truth — it is a source of debate.
- Copy-paste is a scheduled activity. Hours spent moving numbers between files every week is engineering work being done by hand, badly.
Moving on without the big bang
The wrong response is a year-long platform project. The right response is to migrate one report at a time.
Pick the report that causes the most argument or the most manual work. Trace it back to its sources, build a pipeline that refreshes it automatically, and agree a single definition for every metric on it. Ship that, let people live with it, and then take the next report.
Two things happen along the way. The obvious one is that reporting gets faster and stops breaking. The more valuable one is that your team starts trusting the numbers again — because everyone is finally looking at the same ones.
Spreadsheets do not disappear in this world; they go back to what they are good at. Analysis, exploration, one-off questions. The load-bearing work moves somewhere built to bear load.