The Spreadsheet Graveyard

A Graveyard of Good Intentions

Every file on every desktop was created by a smart person solving a real problem. The Raj_edits version happened because Raj needed a number on a Tuesday and the MASTER was locked. The DONT_EDIT.xlsx exists because someone edited it. Each fork is rational. The aggregate is a graveyard.

The problem is not that people made copies. The problem is that the original system assumed a single shared spreadsheet was enough infrastructure for a business. It wasn't. It never was. It was what you could afford when you were three people.

Three Symptoms, One Cause

First symptom: your Monday number doesn't match your Friday number. Second: two different leaders present the same metric with different values at the same meeting. Third: you introduced a new employee last quarter and they asked an obvious question that revealed your reporting had been wrong for 14 months.

All three symptoms trace to the same cause: data that lives in files instead of in a system. Files are artifacts. Systems are processes. You need the process.

When everyone owns the data, no one owns the data.

[The Forge installs a single ledger. Every downstream report pulls from it. Disputes collapse because nobody is reading a stale file.]

The Migration Is Not the Hard Part

Moving the data is a weekend. Changing the habit is the quarter. People reach for the file because the file is what they know. The system wins only when it is measurably faster and more trustworthy than the file, and that is an engineering problem, not a training problem.

The Forge's rule: if the new system is not the path of least resistance within two weeks of install, the install has failed. Good interfaces kill spreadsheets. Bad interfaces spawn seventeen more.

[A 30-day migration, run like a demolition. Old files are archived read-only; they do not die of natural causes.]

What Replaces It

A ledger, an API, and a thin view layer. The ledger is the system of record, immutable, time-stamped, source of all reporting. The API is how humans and agents write to it. The view layer is how people read from it, in whatever shape they need, dashboard, Slack message, email digest, voice query.

You do not ask people to stop making spreadsheets. You make the spreadsheet obsolete by making the ledger more useful. This is the difference between policy and architecture.