One resignation away: the risk nobody has measured

Every firm holds its breath somewhere. A billing process that lives in one person's head. A client relationship only the founder can hold. A month-end close that works because one analyst remembers the seventeen manual steps. When that person takes leave, the firm slows down. When they resign, a function breaks.

I watched this play out early in my career, from the inside. I joined a firm to replace their best employee, and he was already gone by the time I started. The entire client-delivery process had lived in his head. No documentation, no workflow, no handover. I rebuilt what I could from scratch while learning the job itself, and it was not enough in the time available. Years later I learned the business itself had not survived. It lost its best employee, then his replacement, then eventually itself.

Here is the reframe that changes how you handle this. Key person dependency is not a staffing inconvenience to be managed with retention bonuses. It is a structural risk with a commercial price, the same category as a governance gap or an untested recovery plan. Treat it that way and the fix becomes obvious: build the structure so the knowledge lives in the system, and the system empowers the person.

The strongest firms I work with do three things. They map where each critical function actually lives, in a system or in a head. They document and systemise the ones in heads, starting with the most commercially exposed. And they test the result the honest way, by having someone step away and watching whether the function holds.

A business that runs on one irreplaceable person is a single point of failure waiting for its moment. A business built on systems that empower its people holds its shape when anyone steps away, including the founder. That is the difference structure makes.

← All insights