Your Busiest Person Is A Risk

Somebody in your venue is the person everything routes through. You know who.

That concentration reads as reliability. It is also the largest operational risk you have, and it grows quietly.

How it forms

Nobody designed it. Competence attracts work, and the fastest way to get something done is to ask the person who already knows how.

Each individual instance is correct. The accumulation is not.

⚠️ The person themselves rarely objects, because being needed is not unpleasant — right up until the point it is.

What it actually costs

Holidays become negotiations. Or they do not happen, which is worse and ends the way it usually ends.

Illness becomes a crisis. ⚠️ You find out what only they knew on the day they are not there, which is the most expensive possible moment to discover it.

They cannot be promoted. They are load-bearing where they are. A structural cap on somebody good, which they will eventually notice.

Their judgement stops being checked. When one person is the only one who knows how something works, nobody is in a position to question how they do it.

The fix, in four weeks

Not documentation projects. Four weeks of small moves.

Week one: list what only they know. Ask them; they will produce it quickly and it is usually shorter than feared. Six to ten items.

Week two: pick the three with the worst consequences. Supplier relationships, a system nobody else can operate, the thing that happens monthly that only they do.

Week three: have somebody else do each one, once, with them watching. ⚠️ Doing beats documenting. A written procedure nobody has executed is a document, not a capability.

Week four: write down only what the doing revealed was missing. Short, specific, and now accurate.

The obstacle

It is slower the first time, always, and the venue is busy.

⚠️ This is the entire reason it never happens — and the reason it stays undone is exactly the reason it must be done. If you cannot spare them for a fortnight, you have already established the problem is real.

The test

Send them on holiday for a week and do not call them.

Whatever breaks is your list. ⚠️ Do this deliberately, while it is a test, rather than accidentally, while it is an emergency — and tell them that is what it is, so the week is not spoiled by waiting for the phone.

What not to do

Do not spread the load by taking work away from them without saying why. It reads as demotion.

⚠️ Frame it as what it is: you are removing a cap on them and a risk on you. Most people respond well to that, and badly to quietly being made less central.

Three to hold

Tasks only one person can do. The list. ⚠️ Most operators have never written it and are surprised by the length.

Days since your key person took consecutive time off. A number that is usually uncomfortable.

Tasks moved from one person to two, quarterly. Whether anything is actually changing.

Where the record has to sit

Most of what the key person knows is not written anywhere, which is what makes them the key person. The parts that can be — supplier terms, recurring tasks, guest history — are the parts to move first, because those are the ones that can live somewhere other than a head.

tasteck keeps recurring tasks, guest notes, and shift history on shared records, so the transferable half of what one person knows stops being personal knowledge.

They are not a risk because they are unreliable. They are a risk because they are the only one.