The System Is Bigger Than the Person

There’s a quiet trap that most growing businesses fall into without noticing.  A capable person joins, takes ownership of a function, and gets very good at it.  Over time, the way they do things becomes the way things are done.  Nobody writes it down because nobody needs to, the person is right there.  Ask them a question and you get an answer in thirty seconds.  Why would you spend hours documenting something you can just ask about?

The answer, of course, is that one day you won’t be able to ask.  And on that day, the thirty second answer becomes a three week reconstruction project, done under pressure, usually by someone less qualified to do it, while customers and colleagues wait.

This pattern compounds quietly over years.  Early on, when the business is small, everyone can see everything.  There’s no real gap between what’s in someone’s head and what everyone else understands, because the team is small enough that knowledge travels by osmosis.  As the business grows past a certain point, that stops being true.  Functions specialise, people go deep into their own areas, and the gap between what one person knows and what everyone else knows widens without anyone deciding it should.  By the time it’s noticeable, it’s usually already a genuine risk, not a theoretical one.

Knowledge concentration feels efficient. It isn’t.

A business that runs well because of one person’s judgement isn’t actually running well.  It’s running on a single point of failure that happens to be performing.  That’s a fragile position, even when everything looks fine on the surface.  The measure of a genuinely well run operation isn’t how good your best person is.  It’s how little the business notices when that person takes two weeks of leave, gets promoted, or leaves altogether.

This is uncomfortable to hear if you’re proud of the people you’ve built the business around, and you should be proud of them.  But pride in your people and dependency on your people are two very different things, and it’s worth being honest with yourself about which one you’re carrying.

There’s also a subtler cost that shows up long before anyone resigns.  When one person holds the knowledge, they also, whether they intend to or not, hold a degree of leverage over how decisions get made.  Growth gets bottlenecked through their availability.  Other team members hesitate to make calls in that person’s area because they don’t have the full picture, so everything routes back through one desk.  A business built this way can grow revenue for years while its actual capacity to make decisions barely grows at all, because capacity was never distributed in the first place, it was concentrated.

What Preparedness Actually Looks Like

We worked with a client earlier this year on exactly this problem, uncovered through an 1-day diagnostic, not because someone had already left, but because the owner could see the risk building.  Key operational knowledge, the scheduling logic behind day-to-day production, supplier relationships, quality checkpoints that had never made it onto paper, sat almost entirely with two long-serving team members.  Both were highly capable.  Both were also, eventually, going to move on, retire, or simply be unavailable at the wrong moment.

The starting point wasn’t a whiteboard session or a generic template downloaded from the internet.  It was systematically capturing how decisions actually got made, not the theoretical process described on a wall chart, but the real one, including the judgement calls that experienced people make without consciously thinking about them.  Why does the sequencing change on a particular type of job.  Which suppliers get called first when a delivery slips, and why those ones specifically.  What does a quality issue that’s worth stopping the line for actually look like, compared to one that gets flagged and monitored.  None of this had ever been written down, because it had never needed to be, until it did.

The difference between a binder and a drawer

There’s an important distinction here.  Plenty of businesses have a folder somewhere labelled ‘procedures’ that nobody has opened in two years.  That’s not preparedness, it’s paperwork.  What actually works is closer to a drawer that gets opened and used, current, specific enough to be useful in the moment, and structured around the decisions someone would actually need to make, not a generic checklist copied from a template.

For this client, that meant the documentation wasn’t a project that finished and got filed.  It became part of how the operation ran day-to-day, referred to by the very people who’d helped create it, which is usually the best sign that documentation is actually working rather than just existing for its own sake.  It also meant revisiting it, because a document that’s accurate on the day it’s written and never touched again drifts out of date within months.  Operations change, suppliers change, people learn better ways of doing things.  A drawer only stays useful if someone’s responsible for keeping what’s in it current.

The payoff arrived sooner than expected.  When a scheduling change meant one of those two key people was unexpectedly unavailable for several weeks, the business kept moving.  Not perfectly, and not without some extra oversight from the owner, but without the kind of disruption that would previously have brought a whole workstream to a stop.  That’s the entire point.  Preparedness doesn’t mean nothing goes wrong.  It means a manageable problem stays a manageable problem, rather than becoming a crisis that eats weeks of the owner’s own time while everything else waits.

It’s also worth being honest about what this isn’t.  It isn’t a claim that documentation replaces good people, or that experience stops mattering once it’s written down.  Judgement, relationships and instinct built over years are genuinely valuable and no document fully captures them.  The goal isn’t to make people interchangeable.  It’s to make sure the business doesn’t fall over while someone new is building that same depth of experience, and to give the next person a running start instead of a blank page.

The Question Nobody Asks: Do You Need Like for Like?

Here’s the part most owners miss entirely.  A departure, planned or otherwise, is one of the only moments you get a genuinely clean opportunity to ask whether the role should even exist in its current form.

Most businesses don’t ask this.  Someone leaves, and the instinct is to replace them, quickly, with someone as similar as possible, because that feels like the safest and fastest path back to normal.  It’s understandable, there’s real pressure to fill the gap and stop the bleeding.  It’s also frequently a missed opportunity, and often an expensive one, because you end up paying to recreate a role shaped around a person who’s no longer there, rather than a role shaped around what the business actually needs today.

Roles calcify around the person who fills them

Over years, a role tends to absorb the particular strengths, habits and blind spots of whoever has been doing it.  A salesperson who’s brilliant at relationship building but weak on process ends up with a role description that quietly emphasises relationships and glosses over process, simply because that’s what’s been getting done.  A production lead who’s strong on the floor but avoids the admin side ends up in a role where the admin side just doesn’t happen properly, and everyone adjusts around that without ever naming it.  When that person leaves, hiring ‘the same but better’ just recreates the same imbalance with a new name attached, and the business inherits the same gap all over again.

The better question, and the one we asked with the client above when a long-serving operations lead began winding toward retirement, is what the business actually needs the role to do now, not what it needed five or ten years ago when the role was first shaped.  The business itself had changed considerably in that time.  Volume had grown, the product mix had shifted, and a role built around the operational demands of years earlier no longer matched what the business needed from that seat today.

Sometimes the answer is a genuine like for like replacement, and that’s a perfectly valid outcome of asking the question properly, it just shouldn’t be the default assumption.  Often it isn’t the right answer though.  Sometimes it’s two part-time or more specialised roles instead of one full-time generalist.  Sometimes it’s a redesigned role with different accountabilities that better reflect where the business is now.  Sometimes a piece of what that person did shouldn’t be a standalone role at all, it should be built into a system or a process so it doesn’t depend on a person the next time either, closing the loop back to everything above.

None of this is possible to see clearly while someone is still in the seat, doing the job the way they’ve always done it, competently enough that nobody stops to question the shape of the role itself.  That’s not a criticism of the person, it’s simply how organisations work, the person in the seat is rarely the right person to redesign the seat.  A departure forces the question whether you’re ready for it or not.  Businesses that treat it purely as a hiring exercise, moving as fast as possible to fill the vacancy, skip past the one moment they had to ask it properly, and usually don’t get another clean shot at it for years.

Building the Drawer Before You Need It

The businesses that handle key departures well didn’t get lucky.  They did a small amount of unglamorous work well before they needed to, and it’s genuinely accessible work, not a multi-year transformation project.  None of what follows requires a big budget or months of downtime.  It requires deciding it matters enough to prioritise ahead of the next urgent thing, which is precisely why most businesses never get to it until they’re forced to.

Start with what would actually hurt

Not every part of every role needs documenting equally.  Start with the two or three things that, if that person vanished tomorrow, would cause the most immediate damage.  Pricing logic.  Key supplier or customer relationships and the history behind them.  The judgement calls that look automatic from the outside but are actually built on years of pattern recognition.  That’s where the real risk concentrates, and it’s usually a much shorter list than owners expect once they sit down and actually make it, rather than a vague sense of unease about everything at once.

Make it usable, not comprehensive

A five page document someone will actually open under pressure beats a fifty page manual nobody will read.  Write it for the person who’ll be using it in a hurry, not for an auditor.  Test it, literally hand it to someone else who doesn’t already know the process and see if they can follow it, then fix the parts where they got stuck.  If it only makes sense to the person who wrote it, it hasn’t done its job.

Assign ownership of keeping it current

Documentation that’s accurate the day it’s written and never touched again is worse than useless, because it creates false confidence.  Someone needs to own keeping it current, ideally the person doing the role, as a normal part of how they work rather than a separate compliance task done once a year under duress.  The businesses that get this right treat updating the drawer the same way they’d treat updating a customer record, an ordinary part of the job, not a special project.

Revisit the role, not just the person

Build in a habit of asking, every couple of years or whenever a role changes hands, whether the role still matches what the business actually needs.  This doesn’t have to wait for a resignation.  It’s a healthier conversation to have on your own terms, with time to think it through properly, than under the pressure of a two week notice period and a business that’s already feeling the gap.

Know where you actually stand

Most owners have a rough sense of where the exposure sits but haven’t tested it properly, because it’s uncomfortable to look at directly and there’s always something more pressing on the calendar.  A structured operational review, or bringing in a fractional COO to run the ruler over it, is usually the fastest way to find out, before it’s forced on you by someone’s resignation letter, exactly where the business is depending on individuals rather than systems, which roles carry the most concentrated risk, and what a realistic, sequenced plan to close those gaps actually looks like.

A useful discipline here is the “bus factor” test borrowed from software teams, if a given person were unexpectedly unavailable for a month starting tomorrow, could the business genuinely function.  For how many people in your business is the honest answer no.  That number, more than any other single metric, tells you where the real exposure sits, and it’s usually smaller and more specific than the general anxiety owners carry about “what if someone leaves” would suggest.