The company that depended on one person

She has been with the company for eleven years. She knows why Monday's report gets adjusted by hand before it goes to leadership, which three customers have payment terms that appear in no contract and what to do when the bank changes its statement format without warning. When she's there, everything works. The day she gave notice, the CEO called an emergency meeting.

It's another composite, and probably the most common scene of this season. Software teams have a blunt name for this risk: the “bus factor”, how many people would have to disappear overnight for a project to stall. In many operations teams at mid-sized companies, the honest answer is one.

We call it commitment. It's also a risk.

The indispensable person is usually also the most committed one on the team. That's why the problem is hard to see: it looks like a strength. But every rule that exists only in their memory is a part of operations the company doesn't control. It can't audit it, improve it, teach it and, above all, it can't scale it.

The signs are recognizable. Some tasks only one person knows how to do. Holidays are planned around the closing calendar. Exceptions get solved by “asking whoever knows”. And every new hire takes months to become autonomous, because what matters was never written down.

A company that depends on its heroes doesn't scale. The one that turns what its heroes know into process does.

Why the manual isn't enough

The classic answer is to ask that person to write a manual before leaving. It gets written, saved in a shared folder and is out of date in three months, because the real process kept changing and the document didn't. Knowledge isn't captured in a text nobody runs.

It's captured when the rules become part of the system people work in every day: what gets matched with what, who approves which amount, what to do with each type of exception. If the system records changes and lets the right people inspect the rules, the team can review them and reduce its dependence on one person's memory.

What changes for the people

There's a reasonable fear behind all this: that writing down the process is the first step toward doing without whoever knows it. It would be wrong to promise that can never happen. The company should explain what will change and design it with those people. Done well, the people holding operations together by hand can stop being the bottleneck and spend more time analyzing, improving and deciding.

And the company, for the first time, owns how it works.

The scenes in these episodes are composites of common situations, not customer cases. Any figures in them are illustrative.