Key-Person Risk

Every business has someone it can't afford to lose. Most of the time it's the founder. Sometimes it's the one salesperson who owns every agent relationship, or the operations manager who is the only person who actually knows how the place runs day to day. Whoever it is, the business has quietly organised itself around a single point of failure - and usually calls it a strength.

If you've worked in more than a couple of businesses, you've seen this. We all have. It's one of the most common patterns there is, and it hides in two ways.

Sometimes it's invisible. Nobody can quite tell you what a particular person does all day - until they're off for a week and a dozen small things stop working, and everyone discovers how much was quietly running through them.

Sometimes it's in plain sight. Everyone knows that if a certain kind of thing needs doing, it's always the same person who does it. The tricky customer, the supplier who'll only deal with one of you, the report nobody else knows how to run. It's never written down as their job. It just always ends up being them.

Either way, the business is depending on a person, not a system. And that has two costs - most businesses only ever feel the first.

The first is fragility. When everything runs through one person, the business is only ever as available as they are. They take a real holiday and the decisions bank up until they're back. They get sick, or poached, or simply resign - and a chunk of how the business works walks out with them, because it was never written down. It lived in their head, in the workarounds and the tribal knowledge everyone just "knows." The strain doesn't only land on that person, either. It lands on everyone left waiting on them.

The second cost you don't feel until the day you try to sell. When a buyer looks at a business that depends on one person, they don't see a business - they see that person, and they have to assume that person might leave. If it's the founder, they've usually just announced they are. The relationships, the judgement, the reason it works at all, tied to someone who may walk out the door. That isn't an asset a buyer is purchasing; it's a risk they're inheriting, and they price it accordingly - a lower multiple, money held back for years and tied to that person staying on, or no deal at all. Due diligence exists to find exactly this: what happens to the business if the person it depends on steps away? If the answer is "it stops," the valuation will say so.

The fix isn't heroics, and it isn't cloning your best person. It's structure. Decision rights, so people know what they can settle without escalating. A meeting cadence that surfaces problems early instead of routing every one of them to the same desk. Documented process for the things that happen often, so the answer to "how does this work" sits on a page, not in a person. Cross-training, so no single departure takes a capability with it. Accountability, not dependency.

Here's the part worth sitting with: fixing this isn't really exit prep. It's just what a good business looks like.

A buyer will pay for it - a business with no single point of failure is worth more, because there's something left to buy when any one person goes. But you don't need a buyer to want this. Key-person dependence is quietly corrosive long before any sale. The person everything runs through is overloaded and can't step back. Everyone else is boxed in, because the authority and the knowledge never reach them. That isn't a healthy culture. It's a bottleneck everyone has politely agreed not to mention.

Spread the knowledge and the authority and three things happen at once. Your best people stop being hostages to their own indispensability. Everyone else gets room to grow into real responsibility. And the business survives any one departure - including, eventually, a sale. Same work, three payoffs. A transaction is just the one that puts a number on it.

The question was never whether your key person will ever leave. It's whether the business - and everyone in it - is better off when it no longer needs them to stay. If the honest answer is no, that's where the work is.