Issue 13 · August 20263 min read

notes from

The most expensive system in your company is the one that only exists in one person's head.

the most expensive system.

Every company has one. A process that runs beautifully, costs nothing on paper, and lives entirely inside one person's head. Ask how renewals get flagged, or how a rush order jumps the queue, or which client gets a call before the invoice goes out, and the answer is a name. "Oh, Dana handles that."

Dana is your most expensive system. Not because of the salary. Because the day Dana is out, the process is out too, and you won't find the documentation, because there isn't any.

how you find it.

You listen for the name. In any ops conversation, count how often the fix for a question is a person instead of a step. "Ask Marcus." "Check with Priya." Each one is a small single point of failure wearing a friendly face.

Then watch what happens on their day off. The requests don't stop. They pool. Someone guesses, gets it wrong, and the cleanup costs more than the original task ever did. That backlog is the invoice for work nobody wrote down.

why nobody fixes it.

Because it isn't broken, right up until it is. The person is good, so the gap is invisible. And the people who could document it are the same ones too busy running it by hand to stop and write it out. The knowledge stays trapped precisely because it works.

There's a quieter reason too. Being the only one who knows how something runs feels a lot like job security. It usually isn't. It's a ceiling. You can't be promoted out of a job nobody else can do.

The goal isn't to replace the person. It's to get what's in their head out where the rest of the team, and a system, can actually use it.

what to actually do.

Pick the one name that comes up most, and spend an hour watching them do the thing. Not a meeting about it. The actual thing. Write down every step, including the ones they don't mention because they've stopped noticing them.

That document is the first draft of a system. Half of it can probably be automated. The other half becomes a checklist a new hire can follow. Either way, the process now lives somewhere other than one person's memory.

You don't have to fix all of them. Just the one that would hurt the most to lose. Find that name, and you've found this Tuesday's work.

real Tuesday