When the Person Who Knows Everything Is on Leave

The short version

"Ask her when she is back" is a decision to defer work for three weeks, taken one item at a time by people who never discussed it.
The items that wait are rarely decisions. They are questions, and the answers exist in what she already wrote and did.
Count the deferred items during the absence. That list is the most accurate map of your team's dependencies you will ever get.
Her StandIn answers from her record while she is off, so the questions resolve and only the genuine decisions wait.

Every team has one. She has been there longest, built the thing everyone depends on, and answers questions faster than any document. When she takes three weeks, the team does not stop, it degrades: items get parked, decisions get postponed, and a queue forms against her return date.

"We have three weeks of 'ask her when she's back'."

What "ask her when she is back" costs

The phrase sounds like patience and functions as a deferral. Each instance is small, defensible, and taken by a different person without reference to the others, so nobody ever decides to postpone a fortnight of progress. It accumulates that way regardless.

The cost lands in three places. Work that waits, which is visible. Work that proceeds on a guess and gets unwound after her return, which is expensive and shows up later as rework. And her first week back, which is spent clearing a queue rather than doing anything, which means the absence effectively costs four weeks rather than three.

Sort what is waiting

During the next absence, sort the parked items as they arise. Three buckets.

Bucket	Example	Should it wait?
A question with an existing answer	"Why did she drop the cache layer?"	No
A decision someone else could make	"Do we accept this schema change?"	No, if authority was assigned
A decision only she should make	"Do we rewrite the pipeline this quarter?"	Yes

On most teams the first bucket is the largest by a wide margin, which is the encouraging finding: the majority of what waits for her is not her judgement, it is retrieval from a record only she can perform.

Keep the deferred list

Make one person responsible for maintaining a visible list of everything parked because she is away. One line each: what was needed, who needed it, and which bucket it falls in.

Two benefits. It stops the same item being parked twice by different people, and it is the most accurate dependency map your team will ever produce. Anything you might design in a workshop is a guess; this list is observed behaviour. Use it as the input to reducing the concentration, as described in reducing dependency on the one person everyone asks.

Answering without her

The first bucket can be emptied while she is away, and it does not require her to have written a handover document covering everything she knows. It requires her record to be answerable.

That is what StandIn does. She has been spending ninety seconds at the end of each day confirming a brief, mostly pre-drafted from the work she already did: current state, open questions, blockers, next actions, and decisions with their reasoning. While she is off, her StandIn answers questions from that record in her words, with a source under every answer, clearly labelled, and it never guesses. Ask why the cache layer was dropped and you get her reasoning with the source underneath. Ask something that is not in the record and you are told so, and pointed at who to ask.

So the first bucket resolves in seconds instead of in three weeks, the second bucket goes to whoever holds the authority, and only the third bucket waits, which is correct. See retire your out-of-office.

What she comes back to

This is the part usually left out of coverage planning, and it is where the last week of cost sits. If the arrangement is that everything waits, her first day back is a queue and her first week is triage, which undoes much of the rest she went away for.

The version that works: she returns to a short list of the genuine decisions that waited, with dates and context, plus a summary of the questions that were answered from her record while she was off, so she can correct anything that was stated wrongly. That is a morning of work rather than a week, and it is the difference between an absence the team absorbed and an absence it merely survived.

Common Questions

What do you do when the only person who knows something is on leave?

Separate the questions from the decisions. Questions about past reasoning and current state can be answered from what they already wrote down. Decisions need either pre-assigned authority or a genuine deferral with a communicated date.

Is it acceptable to contact someone on leave for something important?

For a genuine emergency, through one agreed route, yes. For anything else, no, and the reason is practical: if it is known that they respond, the threshold drops immediately and the leave stops being leave.

How do we reduce this before the next absence?

Keep the deferred list during this one, then work through it afterwards: which items should have been answerable, and which should have had an assigned decider. That produces a specific, evidence-based plan rather than a general intention to spread knowledge.

Should she write a longer handover next time?

A longer handover has diminishing returns, because the questions that arise are the ones nobody anticipated. A daily record of decisions and state covers far more ground than a document written in one afternoon under time pressure.