The Person Everyone Asks First

There is one person everybody asks. Where the spare fuse is, which supplier to call, what happened last time this guest complained, how the till behaves when it does that thing.

They are your most valuable member of staff, and they are also your largest single risk.

What they are actually holding

Not skill — knowledge that exists nowhere else.

Supplier history. Who to call, who is unreliable, what was agreed verbally two years ago.

Guest history. Which regular has an issue with which other regular, who gets which table, what happened at that party in March.

Equipment quirks. ⚠️ Undocumented by definition — the workaround, the sequence, the thing you do not touch.

Precedent. What the venue does in situations that have no policy. They are the policy, and nobody has noticed.

What it is costing you now

Before they leave — the cost is already running.

Everything routes through them. Their day is interrupted continuously, which means their actual job happens badly or late.

Nobody else learns. ⚠️ Asking is faster than learning, so the asking never stops and the knowledge never spreads. This is rational behaviour by everyone involved and it compounds.

Decisions wait for them. On their day off, things that should take a minute take until tomorrow.

They cannot be promoted. The most common outcome: they are too useful where they are, so they stay, and eventually they leave for somewhere that would move them.

Why the usual fix does not work

"Write it down" fails reliably, for two reasons:

They do not know what they know. ⚠️ It is not withheld — it is invisible to the person holding it, because to them it is just how things are.

There is no time. The reason everything routes through them is that they are busy. Adding documentation to their workload is adding work to the busiest person you have.

What works instead

Capture at the moment of asking. When someone asks them something, the answer gets written where the next person will look. ⚠️ One question at a time, by whoever asked — not a documentation project, and not their job.

Rotate the asking. Send the question to someone else first, with them as backup. Slower this week, and the only thing that actually transfers.

Take their days off seriously. A day when they are genuinely unreachable surfaces exactly which knowledge is single-sourced. ⚠️ The list of things that broke is your priority list, and it costs one uncomfortable day to produce.

Give them the credit explicitly. People become the hub partly because it is their standing. Removing the dependency without acknowledging the value is how you lose them faster.

The handover that never happens

When they do leave, the standard plan is a two-week handover.

⚠️ Two weeks transfers the tasks and none of the knowledge. You get the list of what they do. You do not get the supplier who owes you a favour, or the reason nobody books that table for large parties.

The transfer has to have started a year earlier, in the ordinary run of asking questions.

What they hold is the exceptions, not the procedure

The procedure  can be written down
The exceptions  "when this happens, do that" — many, small, individually not worth writing

⚠️ The reason nobody has documented it is that no single piece of it looks worth documenting.

---

What it is costing right now

Their time      their own work does not progress
Nobody else learns   asking is easier than knowing
Their absence slows the night

⚠️ The second is the quietest and the most damaging. People do not fail to learn because of poor teaching — they fail to learn because asking works.

---

The fix that does not work

"Try to work it out yourself first"

⚠️ This raises the cost of asking without increasing the amount of written knowledge anywhere. 　 ⇒ On a busy night it is ignored; on a quiet night it just makes 　 　 decisions slower.

---

Write the answer at the moment it is given

Later, in a batch  cannot be done — nobody remembers the questions
Immediately, one line  twenty lines in a week

⚠️ Twenty lines is a procedure. It is not written; it accumulates.

And the person who asked does the writing

⇒ ⚠️ Do not add documentation duties to your busiest person. If the asker writes it down, the asker becomes the next person people ask — which is the transfer you were trying to engineer.

---

Why the handover never happens on its own

While they are there  nobody has any reason to learn it

⚠️ It has to be forced while they are still present. 　 ⇒ One shift a week where they are deliberately unavailable. 　 ⇒ ⇒ What happens when they are off sick is not a handover. It is an 　 　 　 incident, and the knowledge does not transfer during one.

---

---

Three to hold

Questions per week that only one person can answer. Hard to count precisely; easy to notice. The trend is the point.

What broke on their days off. The single most informative number here, and it costs nothing to collect.

Whether anyone else has done each critical task once. ⚠️ Once is enough to change everything — the second person no longer starts from zero.

Where the record has to sit

Knowledge written into a document nobody opens has not been transferred. It has to sit where the question gets asked — against the guest, against the supplier, against the shift.

tasteck keeps guest notes and change history on the records staff already open during a shift, so what one person knows is visible to whoever is on tonight.

They are not hoarding anything. Nobody ever asked them to write it down, and asking them now is the wrong instruction — start writing down the answers as they give them.

---

Read next

• When the Owner Is Also the Manager
• The Manager Who Cannot Take Holiday
• Your Busiest Person Is A Risk