Skip to main content
Steady at the Top
← All articles

How to keep work moving after a key executive leaves

Keep work moving after a key executive leaves by transferring each live dependency to an accountable owner. Start with decisions and relationships that could interrupt delivery, then test the replacement arrangement. A folder of documents is useful only when someone can use it to perform the work.

A dependency handover map is a working record of the decisions, relationships, access, and exceptions that depend on a departing leader. The term describes the practical method here, rather than an established psychological measure. Its grounding is Daft and Lengel’s (1986) distinction between missing information and unclear interpretation, described in their organizational information paper.

An executive can leave detailed files while leaving the company unable to act. The missing element may be authority to approve a concession, an unwritten supplier arrangement, or the reason a customer receives unusual service. Treat continuity as demonstrated operating capability, with documents supporting that capability.

Apply industrial/organizational psychology, the psychology of work and organizations, to the handover question: can another executive make the necessary decisions and maintain the working relationships after the original owner leaves?

Separate cooperation from continuity

You may hope for an orderly departure. Hope cannot be the control. A leader may have little time, restricted access, a contested exit, or no remaining obligation to help. Design a process that benefits from cooperation without requiring unlimited goodwill.

Knowledge transfer concerns what another person understands. Decision transfer concerns what that person can authorize. Relationship transfer concerns whether a counterpart recognizes the new owner. Completing one does not establish the others.

Keep personnel negotiations separate from operational collection. Employment counsel should advise on obligations, confidentiality, access restrictions, restrictive covenants, and any departure agreement. The handover map describes operating dependencies; it does not determine what departure terms, access restrictions, or employment obligations are lawful in the circumstances. Do not pressure remaining staff to obtain protected material or bypass access controls in the name of speed.

For the broader sequence of an exit, use How to lead executive exits and restructuring with care. The handover map starts after you identify the operational responsibilities that require continuity. It does not decide whether the person should leave.

The dependency handover method

1. Identify the next consequential events

Start with the business calendar. List renewals, board decisions, payroll approvals, product releases, customer commitments, financing milestones, and other events that currently rely on the executive. Use actual upcoming events instead of asking for everything the person knows.

For each event, record the consequence of interruption. A stalled internal report and an unowned customer escalation need different attention. Mark the latest safe decision date and the person who currently knows the work. Distinguish a required deadline from a date someone merely prefers.

Ask a concrete question: “If the executive became unavailable this afternoon, which promise would become difficult to keep tomorrow?” Check the answer with people who perform the work. A title can conceal responsibilities that migrated informally over time.

Avoid turning the map into an unrestricted inventory of private correspondence. Collect information the organization is entitled to use, through approved processes. Have counsel and security specialists resolve unclear boundaries before anyone copies records.

2. Map the full dependency

Give every critical item a row. Include the event, decision required, evidence location, authorized owner, counterpart, exception, and fallback. Record what would make the row unsafe to close. “Documents received” is not an adequate completion condition for an untested process.

Suppose the executive approved unusual warranty settlements. The successor needs the relevant agreement, examples of past decisions, the current approval limit, and the route for larger exceptions. A list of customer names supplies only part of that information.

Separate formal policy from personal practice. If the departing leader made side promises, verify what was said and whether the company accepts the obligation. Label unresolved assertions as unresolved. Do not convert a recollection into a company commitment without checking the underlying record.

Use existing systems as the record where possible. A handover should point to the maintained contract or account file. Copying the same information into several disconnected documents creates another continuity problem when the copies diverge.

3. Assign authority with the work

Name one accountable owner for each live dependency. Supporting colleagues may contribute, but the row needs one person responsible for its next action. Give the owner the authority and capacity required to carry that responsibility.

Temporary ownership is legitimate when it has an explicit end date and escalation route. “The team will handle it” is not temporary ownership. It leaves staff negotiating responsibility while the external deadline approaches.

Check approval limits against Who should decide what, and when should a decision escalate?. Decide what the owner can approve alone, what requires consultation, and what must return to you. Otherwise, the handover can move every unresolved decision into the CEO’s calendar.

Ask the proposed owner to explain the assignment back in operational terms. “I own the renewal recommendation, finance checks the margin, and you approve departures from the price boundary.” That explanation makes gaps visible before a customer discovers them.

4. Transfer relationships through a real next step

Introduce the successor to the counterpart and state the new responsibility. Avoid vague announcements that someone will be “supporting the account.” Say who makes decisions, who handles routine questions, and where urgent issues go.

Use a live piece of work to complete the introduction. The successor can lead the next renewal discussion, approve a pending internal decision, or resolve a supplier question while support remains available. Attendance alone does not demonstrate transfer.

Do not require the departing executive to endorse a personnel decision. A factual introduction is enough. You can preserve dignity without inventing agreement. Coordinate internal wording with How to announce an executive departure to employees so employees and external counterparts receive consistent operational information.

Some relationships will resist the transition. Ask the counterpart what they need to trust the new arrangement. Offer verified evidence of continuity, not an assurance that nothing will change when the work has already changed.

5. Test the handover without the former owner

Run a tabletop exercise using an actual upcoming exception. Ask the new owner to find the evidence, identify the decision boundary, contact the right counterpart, and describe the fallback. Record each point where the process stops.

When safe, complete a normal transaction through the new arrangement. Check access without sharing passwords or retaining permissions that should end. Security controls and continuity planning should support each other through an approved transfer process.

Treat a failed test as useful information. Fix the missing permission, unclear authority, or absent record. Do not mark a row complete because a senior person is embarrassed by the gap. Morrison’s 2014 review examines choices to offer or withhold upward input. Give staff a route to surface gaps without blame.

A handover that looks complete until work starts

Consider a hypothetical operations executive leaving before a major customer renewal. The file contains the contract, pricing history, and meeting notes. The replacement assumes the account manager can approve service exceptions. The account manager assumes approval now sits with finance.

The dependency map exposes a second issue. The executive had promised a special delivery review before renewal, but no one scheduled it. The successor has the information needed to understand the account, yet lacks both a decision boundary and an accepted next step.

You assign the service review to the replacement, confirm the concession threshold with finance, and introduce the customer to the new decision owner. The customer receives a specific date for the review. The row closes only after the meeting occurs and the resulting decision is recorded.

The lesson is a management inference, not a claim that one map prevents every disruption. The map makes particular dependencies inspectable. Its value comes from the quality of the rows and the willingness to test them.

The private-life composite

A founder is at a family dinner when a supplier calls the departing executive’s old number. The supplier then calls the founder’s spouse because the families once traveled together. The founder steps outside and spends the evening reconstructing a payment arrangement.

This is a composite, not a client case. The private interruption reveals a business dependency that the formal exit checklist missed. A personal network has become the fallback operating system. The founder can be grateful for the relationship while deciding the company needs an authorized contact and a documented process.

If stress symptoms persist or affect daily life, speak with a licensed clinician. The operating task remains concrete: remove the need for family channels to carry company decisions.

Close the transition deliberately

Create a short unresolved list with owners and dates. An honest open item is safer than a completed checkbox hiding missing information. Review the list against actual events, then reduce the cadence as the replacement arrangement proves itself.

Kramer’s 1999 review examines barriers to sustaining trust. For this transition, make confidence rest on visible work: a decision made, a counterpart contacted, an exception handled. Praise cooperation without confusing warmth with operating proof.

The same discipline should shape What a CEO should say when announcing company layoffs. Tell people enough to know where work now goes. Keep private exit terms in the appropriate process. A useful closing message names the new owners, remaining temporary arrangements, and the place to report a gap.

Your final question is practical: “Can this work proceed within approved boundaries if the former executive never answers another message?” If the answer is no, keep the dependency open. Continuity is established when the company can perform the work responsibly through the people and systems it now has.

Inspect access and ownership separately

Ask the security owner for confirmation of approved access changes. Ask the operating owner for confirmation that work can proceed. These are separate signoffs. Leaving an obsolete account active is not a valid substitute for transferring access through the right identity.

Where the departing executive used a personal device or personal account, involve the appropriate specialists. Do not ask a successor to improvise collection. The map should record the approved evidence location or an unresolved dependency, rather than encourage a workaround that creates another problem.

Keep the final map available to the people who need it. Limit sensitive personnel information to the appropriate process. A concise operational record should remain useful after the exit itself has faded from attention.

Sources

Steady at the Top