When the spreadsheet becomes load-bearing UI
Every team has a spreadsheet that does too much. That's not the team's fault — it's the moment to redesign.
The spreadsheet starts as a list. Then it gains a formula. Then a conditional format. Then a hidden sheet for lookups. By the time anyone notices, it's running a fifth of the operation.
This is not a discipline problem. It's a design accident.
What actually happened: someone needed something the existing tools couldn't do. They added it manually. The manual step worked. So they added another. And another. Each addition reasonable in isolation; the whole accidentally indispensable.
There's a moment when you can still rip it out. Past that moment, you can only fork it: leave the spreadsheet running, build something parallel, migrate piece by piece. The cost goes up not linearly but with each row of accumulated meaning.
What to look for
A few signals the spreadsheet has crossed over:
- People say "let me check the sheet" instead of naming a tool
- Three columns are hidden by default
- New hires need a half-hour walkthrough just for that file
- The "owner" is the person who happens to know what cell B47 actually means
When you hear these, the work isn't "automate the spreadsheet." It's "design the tool that should have existed."