When spreadsheets become operational infrastructure
A practical way to decide whether a spreadsheet should stay, be improved, or be replaced with software.
Spreadsheets are useful because they are fast, flexible, and understandable. They become risky for the same reasons.
A spreadsheet is usually fine when it supports a small decision or helps a team explore a new process. It becomes operational infrastructure when the business cannot run without it.
Signs the spreadsheet has crossed the line
The warning signs are usually obvious:
- Only one person understands how it works.
- A formula change can affect customers, stock, invoices, bookings, or jobs.
- Data is copied in from other systems and copied back out again.
- The sheet is used as the source of truth for live operations.
- The team has a backup copy because they are worried about breaking it.
At that point, the spreadsheet is doing the job of software without the protections that software should have.
Do not replace it too early
Replacing a spreadsheet too early can waste money. The sheet may still be the best place to learn the workflow.
Before replacing it, ask:
- Is the process stable enough to encode?
- Are the rules clear enough to validate?
- Does the team agree on what the source of truth should be?
- Would a mistake have a meaningful business cost?
If the answers are unclear, improve the sheet and keep learning. If the answers are clear, the spreadsheet may be holding the business back.
What a better system should add
A replacement should do more than make the spreadsheet prettier. It should add things the spreadsheet cannot safely provide:
- Permissioned access.
- Validation before bad data spreads.
- Audit trails for important changes.
- Integration with the systems that already hold the data.
- Clear handling for exceptions and failed steps.
- A reliable view of current operational status.
The right internal tool usually keeps the parts of the spreadsheet that made the workflow understandable, then removes the fragility around it.
The simplest decision rule
If the spreadsheet is used for planning, keep it flexible.
If the spreadsheet is used to run live operations, treat it like infrastructure and review what would happen if it failed tomorrow.
