Skip to main content
Steady at the Top
← All articles

What to ask the departing CEO during your handover

Ask the departing CEO about unfinished commitments, decisions that require context, and relationships the next leader must understand. Tie each answer to an operating record and a receiving owner. A useful handover transfers the ability to act, while preserving uncertainty about disputed events and future results.

Knowledge transfer is the process by which one organizational unit’s experience affects another unit’s knowledge or performance. This paraphrases Linda Argote and Paul Ingram’s 2000 account. Applying the concept to a CEO handover means checking what the receiving team can do with the information, rather than counting documents delivered.

A transfer of authority is different. Board decisions and governing documents determine who may act. A departing CEO’s explanation can inform your judgment without extending their authority after the transition. Clarify those boundaries with the chair before conducting the interview.

Agree on the purpose before the meeting

Tell the departing CEO that the conversation will identify operating obligations and unresolved questions. Explain what will be recorded, who will receive the record, and which subjects require a separate confidential process.

Do not promise confidentiality you cannot support. Personnel information, privileged advice, contractual restrictions, and disclosure duties need appropriate handling. Ask counsel to establish those boundaries where necessary. This interview is general leadership guidance, not a substitute for that advice.

Use a direct opening:

“I want to understand what the organization has committed to, what remains unsettled, and where your experience can prevent avoidable mistakes. We will distinguish records from interpretations. I will not ask you to speak for people who are absent.”

If the departure is disputed, use a chair-approved facilitator where appropriate. Separate an operating handover from an investigation or performance review. Asking one meeting to accomplish all of those purposes makes its output harder to interpret.

The returning founder’s reentry plan provides the wider context. This conversation should produce a usable transfer record within that plan.

Begin with promises, not an autobiography

Ask: “Which commitments will become due before the new leadership team has enough context to evaluate them?” Include promises made to customers, employees, lenders, suppliers, and the board, as relevant to your company.

For each promise, establish the wording, recipient, due point, and operating owner. Request the supporting record. An agreement remembered by one person is an item to verify, not an obligation to dismiss or accept automatically.

Follow with: “What would the other party say we promised?” That question distinguishes the company’s internal interpretation from a possible difference in understanding. Ask who can confirm the other party’s account without creating a new commitment.

Avoid asking only about the largest contracts. A smaller agreement can contain a dependency that interrupts a larger service. Trace consequences through the work before deciding which commitments deserve your attention first.

Use the commitment-and-dependency interview

The commitment-and-dependency interview is a proposed operating method, not a validated psychological assessment. Use numbered sections in the handover record so unresolved items have a clear home.

  1. Capture the next obligation. Ask what must happen next, who expects it, and which record establishes the expectation. Preserve disputed wording rather than silently choosing a version.
  2. Locate the decision dependency. Ask which pending decision prevents the obligation from being met. Identify who has authority to make that decision after the transition.
  3. Recover the reasoning. Ask which alternatives were considered and why they were rejected. Distinguish information available at the time from later knowledge.
  4. Identify relationship context. Ask who needs a direct introduction and what that person needs to know. Record business context without collecting unnecessary private details.
  5. Name the receiving owner. Assign someone to verify and accept each transfer. Receipt of a folder does not establish understanding or readiness to act.
  6. Test the transfer. Walk through a plausible upcoming exception. Ask the receiving owner to explain what they would do and which missing information would stop them.
  7. Close the remaining gaps. Give each unresolved item an owner, a retrieval action, and a review point. Agree on any bounded availability from the departing CEO in writing.

Keep the record short enough to use during an actual exception. Put supporting documents behind it. The central page should direct attention to decisions and dependencies, not reproduce an archive.

Ask for the information that meetings filtered out

Ask how the departing leader’s agenda shaped what reached them. Ocasio’s 1997 theory connects organizational attention with the rules and arrangements that direct decision makers toward issues and answers. Use that account to ask what the review process omitted. It gives the handover interview a question to investigate, rather than supplying evidence that any omission was deliberate.

Ask which recurring problem never reached the formal agenda. Ask which report required explanation before it could guide a decision. Then request an example and its associated record.

Do not treat an account of a neglected issue as settled fact. The departing CEO may be describing a limitation they observed, an interpretation, or a disagreement with colleagues. Preserve the category and identify a verification route.

You can ask: “Where would you look first if next month’s report suddenly looked much better?” The answer may reveal a known measurement discontinuity or a changed operating definition. Check the underlying reporting process before interpreting an apparent improvement.

A composite scene: the folder looks complete

Consider a hypothetical composite. You spend the evening reading a polished transition binder while messages from your partner remain unanswered. The binder contains an organization chart and a list of major accounts. You still cannot tell who can approve an exception when a customer refuses a revised delivery date.

At the handover meeting, the departing CEO explains that one supplier normally accepts a verbal forecast before issuing a written commitment. The relationship owner has also just changed roles. That context appears nowhere in the binder.

You record the practice as an unverified dependency and ask procurement to confirm the supplier’s current process. You do not ask the company to rely on another informal assurance. A receiving owner establishes a documented route for the next decision.

In this constructed example, the value of the interview lies in exposing an operating dependency. The story does not establish that informal arrangements are always wrong, or that the previous CEO intended to hide one.

The test is whether the new team can perform the next necessary action under its own authority. If the answer still requires a private call from the departing leader, the transfer remains incomplete.

Invite correction without conducting a loyalty test

A handover must leave room to correct the predecessor’s account. Within industrial/organizational psychology, the psychology of work and organizations, Edmondson’s 1999 study examines psychological safety and team learning. Apply that lens to the response a participant receives for naming a disputed promise. Neither the interview nor the departing leader can certify how safe the wider team finds disagreement.

You cannot establish a team’s psychological safety through one handover interview. You can design the conversation so correction has a legitimate place. Ask what your preliminary account gets wrong, and record the correction alongside its basis.

Avoid asking the departing CEO to rank colleagues by loyalty. Ask about role demands, observed decisions, and work dependencies. If a response becomes a character judgment, return to an event: “Which decision illustrates that, and what record should we examine?”

A listening tour can gather other perspectives after the handover. Tell participants how their input will be used. Do not circulate one person’s interpretation as an anonymous consensus.

Establish the end of the departing CEO’s role

Clarify whether the former CEO will have a transition assignment, an advisory role, a board role, or no continuing role. Use the company’s actual governance arrangements. Do not imply that a friendly understanding changes formal authority.

The authority reset should tell employees who owns decisions from the effective transition point. If the previous leader remains available for context, explain the route for requesting that context. Staff should not need to infer whose approval matters.

A bounded follow-up arrangement might specify subjects, a contact owner, an end point, and the treatment of new information. Have appropriate counsel review contractual terms and any obligations attached to the arrangement.

When the previous leader declines further involvement, design the transfer around available records and other knowledgeable people. A critical operating process should not depend indefinitely on personal goodwill that has not been committed.

Check the receiving team’s understanding

Ask the receiving owner to describe the next decision in their own words. Which record will they consult? What triggers escalation? Who may authorize a change to the promise? A vague answer identifies more handover work.

Argote and Ingram discuss knowledge within people, tasks, tools, and their interactions. That account supports looking beyond a document repository. Your advisory application is to rehearse a real work situation and examine whether the receiving arrangement can support it.

Do not invent a numerical handover-completion score. Use a visible set of conditions: owner identified, record found, authority confirmed, and unresolved issue assigned. A condition can remain incomplete without invalidating everything else in the record.

Use the chair-CEO working relationship to resolve mandate questions. Keep operational detail with the people responsible for acting on it, subject to the company’s confidentiality rules.

Close with a usable record

Read the remaining questions and their assigned owners back before the conversation ends. Invite the departing CEO to correct factual errors in their account. Preserve a correction history if the record changes after others begin using it.

Then send the authorized internal record through the agreed process. Do not describe silence as approval. Where an obligation remains disputed, state the dispute and the next verification step rather than writing a reassuring conclusion.

Your final handover document should answer an immediate operating question: what can the incoming team now do without relying on the departing CEO’s memory or authority? Use the answer to choose the next transfer task. Keep the history available, while giving the new leadership team a clear basis for its own decisions.

Test one receiving owner with an obligation that has an unresolved exception. Ask what they would consult, who may decide, and when they would return to the departing leader for missing context. If the answer relies on a personal assurance without an authorized arrangement, leave the item open. This makes the interview’s remaining work visible without requiring another broad conversation about the predecessor’s entire record.

Sources

Steady at the Top