A company that writes everything down

Begin in the morning, before anything has gone wrong. The reports are already written. Not because somebody stayed late, but because the procedure for writing them is a document, and the document says where to get the numbers, what shape to put them in, and how to tell whether the result is wrong before anyone reads it. Something ran the document. You read the output over the first coffee, which is an unfamiliar relationship to have with a morning report.

This is the whole idea, and it sounds smaller than it is. A procedure that lives in a document can be run by anything that can read. A procedure that lives in a habit can be run by exactly one person, in one building, in a good mood. The difference is invisible on any given Tuesday. It shows up across a year, in the accumulation.

By mid morning the strange calm arrives. Most companies carry a low background hum, an unspoken is anyone actually doing the thing, and here it goes quiet. Not because everything is fine. Things are not fine, and you will find that out shortly. It goes quiet because the question has an answer you can look up. The thing either ran or it did not, there is a record either way, and the record sits in the same file you would open to change how it runs next time.

Then something breaks, because something always breaks. A step assumes a file exists in a place where it no longer exists. The output looks plausible and is wrong, which is the worst kind of wrong, and it takes you twenty minutes to see it.

Here the day diverges from a normal one. In a company that keeps its knowledge in people, you fix this by telling someone, and the fix lives inside that conversation for as long as they stay. In a company that writes everything down, you cannot fix it by telling anyone, because there is nobody to tell. The repair is an edit. You open the document, you change the step, you add the check that would have caught it, and you write one line about why the check is there so the next reader does not delete it for looking redundant.

That last line is the entire discipline. A rule with its reason attached tends to survive. A rule without one gets tidied away by somebody efficient, and the same failure returns nine months later wearing a different hat.

The compounding is slow and unmistakable. Each break leaves the written system slightly harder to break the same way twice. Nothing gets smarter. The documents simply get less naive.

What you give up is real: the pleasure of a person who just knows, the shortcut of asking instead of reading, the flexibility of a team that quietly works around a bad procedure rather than reporting it. What you get is a company that cannot forget, which turns out to be a stranger and better thing to own than it first sounds.