Pairing and Shadowing That Works

Shadowing has a poor reputation because it is usually done badly: one person works, another watches, and nothing transfers.

For a resilience routine built around “Pairing and Shadowing That Works”, improvement depends on seeing whether backup work happens outside an emergency. Teams can use this project guide to organise practice time and compare planned coverage with actual participation, but the record should prompt a handover conversation rather than become an automatic judgement about an employee.

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.

Why passive watching fails

Watching somebody competent makes a task look simple.

The decisions are invisible: you see what they did, not what they considered and rejected.

And the watcher has no way to discover what they do not understand, because nothing tests them.

What works instead

The learner drives and the expert watches. Reversed from the usual arrangement and far more effective.

The expert narrates their reasoning when they do take over: what they are looking at, what would change the decision.

Questions are expected rather than tolerated, and "why did you do that" is the productive one.

And the learner does the next one alone, with the expert available rather than present.

The sequence

Watch once, to see the shape.

Do it together, learner driving.

Do it alone with the expert reachable.

Do it alone.

Four repetitions for most tasks, spread over weeks rather than compressed into a day.

Time it actually takes

Two to four times as long as the expert doing it alone, for the first few.

That cost is real and it is the reason this does not happen.

Budget it explicitly rather than hoping it fits in the gaps, because it will not fit in the gaps.

Choosing what to pair on

Things that cannot be documented: judgement, feel, dealing with people.

Things that go wrong in interesting ways.

Not routine tasks, which a note covers more cheaply.

The documentation note and this one divide the work: write what is writable, pair on the rest.

When the expert is a poor teacher

Common and not a character flaw. Expertise makes the intermediate steps invisible to the person who has them.

The fix is questions from the learner rather than explanation from the expert.

And having the learner explain back what they understood, which surfaces the gaps immediately.

Making it stick

The learner writes the note afterwards.

They know what was confusing, which the expert no longer does.

And writing it is the test of whether the transfer happened.

What to check

Who drives when you pair — the learner or the expert?

Has anybody done a task alone after shadowing it?

Is the time cost budgeted or expected to absorb?

And does the learner write anything down?

The point

The learner drives and the expert watches.

Reversed from the usual arrangement and far more effective, because watching somebody competent makes a task look simple.

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.

The recurring pattern

The recurring pattern across every section here is the same: dependence forms through sensible individual decisions, becomes invisible because it feels like reliability, and is addressed only after it has cost something. The work that prevents that is small, continuous and unglamorous, which is exactly why it gets deferred.