I once took down the login system for about a hundred people scattered across the country, coast to coast to coast, with the heel of my shoe, and it took me two weeks to find out. In my defence, the thing my shoe took down was a computer I did not know was doing any work at all.
Years ago I worked at a federal department, and under my desk sat a box. An older PC, beige and boxy, no CD drive, just a floppy disk in the front that gnarred and clicked and grumbled to itself now and then, the way old machines do when they are thinking about something. It was part of the furniture. I had taken the job over from the man who retired out of it, and the box had come with the desk the way the stapler and the wobbly chair did. I never once asked what was inside it. Nobody had told me what it did. As far as I could tell, its whole job was to sit there and burp.
So one day I kicked it. Not on purpose, I want to be clear about that. I was changing my shoes under the desk, the way you do, and my heel caught the box and knocked something loose. I would love to tell you I noticed. I did not. The burps stopped, the room got a little quieter, I laced up and got back to work. That is the part I want you to sit with for a moment, because it is the whole point of the story: nothing happened. No error. No alarm. No tap on the shoulder. The box went dark and the day carried on exactly as before, and I went home that night having knocked out something important with my shoe, without the faintest idea I had touched it.
Two weeks went by. Two weeks. Then a voicemail landed, from someone in another department half a country away, left for Guy, the developer I had taken the desk from, retired now but still dropping by for a coffee and a chat because old habits die hard. He wandered over to my corner, a bit puzzled, and mentioned that the remote agents’ login database had apparently stopped answering, and did anyone here happen to know anything about that.
He looked at the dark box under my desk the way you’d look at a friend who’d fallen asleep at the table. Then he bent down, reached behind it, and turned it back on, muttering something I couldn’t quite catch in that unforgettable Gatineau accent of his, the one that got thicker every time he laughed. He did not rush. He picked his coffee back up and sat down while the old beast belched and buzzed its way back to life, and somewhere in the middle of that clicking and gnarring, a hundred people from one end of the country to the other quietly got their access back. Most of them never knew it had gone. Guy had known exactly which box, in which corner, and precisely what it was for, because it had been his. I had inherited the desk. Nobody had thought to hand over the map. It was the most casual rescue I have ever watched.
The box was never the scary part
It would be easy to make this a story about old hardware, or about me being careless, and both of those readings are fair enough. But the thing that actually gives me a chill, all these years later, is quieter than either. That box ran a system a hundred people depended on to do their jobs, and the total documentation for it was Guy’s memory. He had built it and knew it cold, and he had already retired out the door. The only reason it came back at all is that he still liked us enough to drop in for coffee.
The most critical systems in an organization are very often the quietest ones. They earn their invisibility by never failing. Nobody thinks about the box under the desk precisely because it has never once given them a reason to, and so it slides out of the meeting notes, out of the budget, out of everyone’s head, until the day it goes silent and you discover you had no idea what you were about to lose. The failure is rarely the machine. The failure is that the map of what keeps the lights on lived in exactly one person’s head, and one day that person retires, or takes another job, or simply moves on.
I think about that box every time I open the hood on a system somebody has run for years and inherited from somebody else. The good news is that finding your own box under the desk is completely doable, and it is a far better afternoon than the one where you find it by accident. It is most of what a real site audit is actually for: not a tidy report of what is broken, but an honest map of what is quietly load-bearing, written down somewhere other than one person’s memory. It is the same discipline I wrote about in a piece on inheriting a site, where the most dangerous line of code on the whole project was the one that looked most like junk.
So here is the only question the story really leaves you with. Somewhere in your organization there is a box under a desk. It might be an actual machine, or a spreadsheet nobody opens, or a single person who is the only one who knows how a thing works. Do you know what it is before it goes quiet? Because the difference between a two-minute fix and a two-week outage is almost never the hardware. It is whether somebody wrote down what the box was for while the person who knew was still around to ask.
Leave a Reply