Turn on the flashlight. The first thing it lands on is a spreadsheet.
It has no official owner. It appears in no process document, no tool inventory, no onboarding deck. IT doesn’t know it exists. Finance definitely doesn’t know it exists. And everyone — *everyone* — uses it. Ask who created it and you get shrugs, or the organizational equivalent of geology: *it was here when I started.*
That spreadsheet is running part of your company. Let me tell you how it got the job.
—
The origin story is almost always the same, and there’s not a villain in it anywhere.
At some point, the official process stopped fitting the actual work. Not because it was badly designed — because reality updated and the process didn’t. A market shifted. A tool changed. A customer broke an assumption. The document stayed frozen at the moment somebody last had time to write it.
Now put a capable employee in that gap, with work due Friday. Her options: file a ticket into a queue, raise it in a meeting and spend political capital she’s not sure she has, or remember what happened to the last person who suggested the process didn’t work. Or — twenty minutes in Excel, and the work ships.
She builds the spreadsheet. It works. A colleague asks for a copy. The copy gets a tab. Within a year it’s load-bearing, and nobody ever decided anything.
I watched the mature form of this at one client: four spreadsheets, four different teams, each one cloned fresh every week. No version control. No owner. And the detail I’ve never forgotten — when I asked about it, nobody was embarrassed, because nobody saw it as unusual anymore. The adaptation was so complete it had become the landscape. *That’s just how the numbers work here.* (The full story of that ecosystem is on the blog. It deserves its own telling.)
—
Here’s the reframe this entire chapter hangs on.
The conventional read of the unofficial spreadsheet is disobedience. Process non-compliance. A discipline problem, a training problem, a culture problem — some flavor of *the team isn’t following the system.*
Wrong read. The team didn’t abandon your process. Your process abandoned them first — and they responded the way capable people always respond: they adapted. What you’re looking at is not resistance. It’s not laziness. It is resourcefulness aimed at the wrong target, because the right target — fixing the official system — was never actually available to them. No authority to change it, no bandwidth granted for it, or a memory of the last attempt going nowhere.
People don’t stop doing the work when the system fails. They stop doing the work *in the system.* The work goes underground and keeps shipping. That’s what a Shadow System™ is: the unofficial system your people actually use when the official one stops matching reality.
And it is never just one spreadsheet. Follow the thread and you find the Slack channel that became the real project tracker, the personal drive that became the real file system, the one person who became the real escalation path. An entire second operating system — the infrastructure of the second company from the beginning of this manifesto. This is where that company keeps its tools.
—
The instinct, once you spot one, is to kill it. Delete the spreadsheet. Mandate the CRM. Send the email with *going forward* in it.
Hold that instinct, because it’s aimed at the confession instead of the crime. The spreadsheet isn’t your problem. The spreadsheet is your *evidence* — and that’s the next section.
Nobody officially owns the spreadsheet. The spreadsheet unofficially owns the process. It got the job the way every shadow hire does: it showed up, and it did the work.