The Questions That Reveal It

The map in the previous note is the structured version. These questions get most of the same information in a conversation, and they work when a formal exercise would feel heavy.

The principles in “The Questions That Reveal It” become easier to maintain when ownership and time spent are visible. Teams evaluating long-term time tracking software can use it to coordinate recurring work, identify tasks concentrated on one person and plan realistic backup capacity, while treating the data as a prompt for knowledge transfer rather than as a substitute for speaking with the people who do the work.

For an independent benchmark, compare the local approach with Ready.gov business preparedness guidance; the useful test is whether ownership, access and recovery remain proportionate and explainable when the usual expert is absent.

The eight

"If you were off for three weeks with no phone, what would break first?"

"What do people ring you about that they should be able to work out themselves?"

"What do you do that you have never explained to anybody?"

"Whose approval is needed for things you can approve?"

"What would a new person take longest to learn?"

"Is there anything only you can log into?"

"What do you know about a client that isn't written anywhere?"

"What are you dreading being asked about while you're away?"

Why these work

They ask about specific situations rather than about capability, so they do not sound like an assessment.

They invite the person to volunteer rather than to defend.

And the last one in particular produces honest answers, because everybody has something they are quietly worried about and few people have ever been asked.

When to ask them

Before somebody takes a long holiday, which is the natural occasion.

In a one-to-one, one or two at a time rather than as a list.

When a new person joins, about the person training them.

And after any near miss: somebody was ill for a week and something nearly went wrong, which is the moment the conversation is easiest to have.

What to do with the answers

Write them down as they come. You will not remember and the specifics are what matter.

Add them to the map.

Then pick one — the one with the worst consequence and the smallest effort — and fix that. The note on what to spread first covers choosing.

Asking the founder

Harder, and the same questions work if somebody is willing to ask.

If nobody in the organisation can, an accountant, a board member or an outside adviser frequently can, and it is a reasonable thing to raise with them.

The holiday question is the one that lands: an owner who has not taken two uninterrupted weeks in five years usually knows what that means.

What the answers usually reveal

More access problems than knowledge problems, which is good news because access is the easiest to fix.

A handful of client relationships held personally.

One or two processes genuinely understood by one person.

And several things everybody assumed were documented and are not.

What to check

Have you asked any of these of anybody?

Have you asked them of yourself?

When somebody last went away, what did you worry about?

And did you write it down afterwards, or just feel relieved when they came back?

The point

Ask what they are dreading being asked about while they are away.

Everybody has something they are quietly worried about and few people have ever been asked.

Underlying all of this

Everything in this collection reduces to four habits: know where the dependence sits, do the cheap fixes first, use the absences that already happen as rehearsals, and decide deliberately about what remains. None of it requires a framework, a tool or a consultant, and an organisation that does those four things consistently is substantially harder to damage than one with a succession document nobody has read.