Executive development

Building a Succession Shadowing Schedule for an Executive's Deputy

A succession shadowing schedule for an executive's deputy, covering the learning goals, the decision moments, the observation notes, and the tested handover.

4 min readHireExecutiveTeam editorial
Building a Succession Shadowing Schedule for an Executive's Deputy article illustration
Table of contents
  1. Define what the deputy must learn
  2. Match shadowing to real decision moments
  3. Record the observations and the gaps
  4. Hand over a tested routine
  5. Related resources
  6. Frequently asked questions

Define what the deputy must learn

List the decisions the executive makes in a normal quarter and mark the ones the deputy must be able to handle within a year. A shadowing plan that covers only meetings teaches the deputy to watch rather than to decide. Record the decision, the current owner, and the target level. The list should come from the executive's own calendar and approval records.

Separate the knowledge that can be read from the knowledge that has to be observed in the room. A policy manual can explain an approval threshold, but it cannot show how the executive handles a disagreement between two function heads. Record the topic and the learning method. The plan should use shadowing where observation adds something a document cannot.

Ask the executive which parts of the role they find hardest to delegate and why. A shadowing schedule that avoids the difficult work prepares the deputy for the easy half of the role. Record the concern and the reason. The answer should shape the first month of the schedule rather than the last.

Agree how the deputy's existing workload will be covered during the shadowing days. A deputy who attends every session while their own team waits is being set up to fail. Record the cover and the owner. The schedule should be realistic enough to survive a busy quarter.

Match shadowing to real decision moments

Attach each shadowing session to a live decision rather than to a general meeting category. A deputy who sits in a weekly operations review learns the rhythm but not the trade-off. Record the decision, the date, and the role the deputy will play. The session should have a defined purpose before it is added to the calendar.

Rotate the deputy through the finance, people, client, and risk decisions rather than concentrating on the function they already know. A deputy who is strong in operations may never see how a pricing exception is approved. Record the rotation and the gap. The schedule should deliberately cover the weaker areas.

Give the deputy a small decision to own in each area before the shadowing period ends. An observer who never decides does not discover where their judgment differs from the executive's. Record the decision and the review. The review should compare the deputy's reasoning with the outcome, not only the answer.

Include the informal moments where the executive gathers information, such as the call before a board meeting or the conversation after a client visit. A plan built only from scheduled meetings misses how the executive tests a decision. Record the moment and the access. The deputy should understand which conversations are appropriate to join.

Record the observations and the gaps

Ask the deputy to write a short note after each session that records the decision, the options, and the reason for the choice. A note written weeks later turns every decision into an obvious one. Record the note and the date. The executive should read the note and correct any misunderstanding.

Record the questions the deputy could not answer and the information they did not have access to. A gap in access is a design problem in the succession plan rather than a failure of the deputy. Record the question and the missing source. The plan should close the access gap before the next session.

Review the notes monthly with the executive and choose one area where the deputy will take the lead. A plan that only accumulates observations never transfers authority. Record the area and the date. The handover should be small enough to test and important enough to matter.

Keep the notes in a restricted development file rather than in the general executive records. A candid note about a deputy's judgment can be damaging if it circulates without context. Record the location and the access list. The file should be reviewed when the succession plan changes.

Hand over a tested routine

Let the deputy run one recurring executive routine, such as the weekly priorities meeting, for a full cycle before the plan is called complete. A single observed meeting does not show whether the deputy can sustain the rhythm. Record the cycle and the feedback. The executive should stay available without taking over.

Ask the people who work with the executive whether the deputy's decisions were clear and timely. A handover that satisfies the executive but confuses the team has not transferred the role. Record the feedback and the source. The comments should be shared with the deputy in a form they can act on.

Test the handover during a short absence rather than only in parallel with the executive present. A deputy who has never been the only decision maker has not been tested. Record the dates and the decisions made. The test should include at least one escalation.

Close the cycle by updating the succession plan with the areas the deputy now owns and the areas that still need support. A plan that remains unchanged after a year of shadowing is a record of activity rather than a transfer. Record the update and the next review date. The next deputy should begin from a tested schedule.

Read also: executive office coverage plan and decision log.

Frequently asked questions

Should one assistant support the whole executive team?

Sometimes. It works when priorities are clear and executives share one operating rhythm.

What should happen before a consult?

List the meetings, inbox rules, recurring reports, and decisions that need support.

Ready to define the role?

Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.

Book a consultation