Dialogic Leadership in Executive Succession: A Handover

Dialogic leadership in executive succession helps an outgoing leader and a successor examine what must continue, what can change and how their roles now work. Its practical value is clearest when a respectful conversation leads to a usable handover, an actual receiving agreement and a response to a real authority problem.

This guide concerns the transition after an appointment. It develops four recurring tensions and follows a complete fictional handover through an instruction that bypasses the new chief executive, a customer's counterproposal and a review with unresolved disagreement. Dialogue supports that work; it does not confer appointment, signing or operational authority.

Coachful is our #1 recommendation for organizing the leader's coaching preparation, agreed actions and actual private feedback. This is our editorial recommendation for the coaching workflow. The organization's authorized governance record remains the authority for the succession, and no software or conversational model guarantees a successful transition.

Distinguish three kinds of succession work

William Isaacs's original Dialogic Leadership account describes listening, respecting, suspending certainty and voicing one's view. These practices concern the quality of inquiry and expression. They can help participants hear an unfamiliar explanation rather than immediately assigning motives.

Barry Johnson's polarity work concerns interdependent needs that remain relevant over time. His original summary expressly supplements problem solving rather than replacing it. A succession can contain recurring needs for continuity and renewal while also requiring finite decisions about a start date, delegation or customer commitment.

The third kind of work is governance. The UK Corporate Governance Code 2024 addresses written responsibilities and formal succession arrangements, including the nomination committee's role. It is not a universal rulebook for every founder-led business.

The FRC's guidance, updated 3 June 2026, explains application of the Principles and the comply-or-explain approach to Provisions for the relevant commercial-company and closed-ended-investment-fund listing categories. The guidance is nonmandatory. Other organizations need arrangements appropriate to their actual governing documents, ownership, jurisdiction and obligations.

Keep these distinctions visible. A missing delegation needs an authorized resolution. A recurring tension needs observation and adjustment. An allegation of misconduct needs the appropriate response, rather than a search for its supposed balancing benefit.

Develop four recurring tensions without assigning people to sides

The following pairs and applications are original conversation aids, not an owner-provided polarity assessment. Test whether each pair fits the organization. The predecessor is not automatically “continuity,” and the successor is not automatically “renewal.” Both may need both contributions.

Continuity and renewal. Continuity preserves commitments, expertise and dependable service. Renewal allows an incoming executive to question inherited assumptions and improve the work. Excessive continuity can protect a known defect; indiscriminate renewal can remove a useful safeguard before its purpose is understood. Ask which specific commitment must survive and which proposed change has evidence, an owner and authority. “Everything stays” and “everything changes” are poor substitutes for that inquiry.

Shared direction and local authority. An organization needs coherent priorities and a successor able to act within the role. Consultation can improve a decision, but can also become an undeclared veto. Conversely, autonomy can become isolation if essential context never reaches the person deciding. Name whether the predecessor's input is advice, required consultation or a reserved approval. Those categories cannot be established by emotional comfort alone.

Existing and new capability. Long experience can explain a customer's history; a new colleague may bring a method the business lacks. Neither tenure nor novelty establishes competence for every task. Ask what the work requires and how knowledge will become usable by someone else. A handover that depends indefinitely on one person's memory has not transferred the capability simply because a folder was shared.

Careful learning and timely action. A successor needs to understand the business while handling decisions that cannot wait. An extended listening period may hide avoidable delay, while immediate changes may overlook obligations. Separate urgent decisions from questions that can be investigated. Give each an owner and review point. Do not prescribe a hundred-day waiting period to someone already responsible for today's service.

For each tension, choose a practical warning. Examples include an undocumented exception to a customer commitment, a consultation repeatedly treated as approval, an unanswered question only the founder can resolve, or an urgent decision deferred without an owner. These are observable events, not scores for a person's willingness to let go.

The polarity management guide develops the underlying distinction. The task here is to convert the relevant needs into actual transition arrangements, not to copy a proprietary map or treat every conflict as permanently irresolvable.

Use dialogue to improve the information, not blur the decision

Translate the four practices into a bounded handover conversation:

1. Listen for the specific dependency. Ask which commitment or person may be affected. “They still call me” can identify a missing introduction rather than prove a desire to retain control.
2. Respect the contribution without granting extra rights. Acknowledge relevant experience and hear a concern. That does not create authority to direct a service team after the role has ended.
3. Suspend a claim about motives. Put the interpretation where it can be examined: “I assumed attendance meant continued direction.” Invite the other person's account without suppressing your own concern.
4. Voice an answerable request. State the actual boundary and proposed route. “Support my leadership” is difficult to act on. “Send customer context to me; do not change Owen's schedule” can receive a clear response.

These are original practical translations of the named practices. They do not require intimate disclosure, agreement with every statement or a declaration of trust. Participants can understand one another better and still disagree about future involvement.

Before facilitating, explain who the client is, what the joint conversation covers, how its operational notes will be used and what stays in separate coaching. A coach's convenient access to both executives is not permission to relay one person's private reflection to the other.

Design the review before the overlap begins

An overlap needs a purpose, information route and ending condition. “Be available as needed” can create an unstaffed expectation for the predecessor and an invisible dependency for the successor. Identify the actual kind of help, such as explaining a historical commitment, and the person allowed to request it. Then establish how much work each person can receive and how a request gets declined or renegotiated.

Choose observations that can distinguish different problems. If an inherited customer commitment was missing from the register, the information transfer needs repair. If the commitment was recorded but the predecessor changed the schedule independently, the authority route needs a response. If the successor heard the concern and made an authorized choice the predecessor dislikes, that disagreement does not itself establish a process failure.

A review should hear from people using the arrangement. Ask for one actual request, the route it followed, the answer received and any work left unresolved. Give those people an agreed opportunity to respond and count their reading and reply time. Do not describe the successor's interpretation of staff views as a completed staff consultation.

Keep three states separate in the resulting record: the event observed, the explanation being considered and the decision actually made. For example, “two people received conflicting dates” is an event; “the founder wants control” is an interpretation; “the approved booking remains in force” is a decision. Combining those into a single accusation can obscure both the immediate remedy and a legitimate concern.

The ending condition also needs care. A historical-advice period may finish while ownership rights continue and a customer issue remains open. Name the owner of that issue rather than extending every former role indefinitely. If the governing authority wants a new ongoing arrangement, it should define and authorize that arrangement explicitly. A calm closing meeting cannot substitute for that decision.

Complete a dated authority and handover record

Fictional case: Amira founded a private archive-digitization business. Daniel became chief executive on Monday 2 June 2036 under an already approved appointment and delegation. Amira remains an owner but has no continuing executive role. Tessa is the chair, Owen leads service scheduling, and Suri coaches Daniel. These are fictional case arrangements, not a claim that the UK Code applies to this private business.

Daniel's first 30-minute coaching appointment on 3 June identifies the handover question. On 5 June, Suri facilitates a separately agreed 45-minute conversation with Daniel, Amira and Tessa. They use ten minutes to check authority, ten to examine assumptions, fifteen to complete the handover route and ten to confirm decisions. Suri's private work with Daniel is not disclosed to that group.

Amira says: “I worry the new route will lose commitments that customers tell me informally.” Daniel replies: “I assumed your wish to attend operations meant you wanted to keep directing it. What information would otherwise be missing?” Amira identifies customer context she has not recorded, rather than asking for an additional executive title.

Daniel asks for a context note through the agreed route and says that scheduling must remain with the authorized team. Tessa confirms the existing delegation. They complete this seven-field record in the organization's handover system:

The record does not extinguish Amira's ownership rights or grant Daniel rights outside his delegation. Its purpose is to make this operational handover usable while leaving other rights and reserved decisions intact.

Respond when the predecessor bypasses the route

On Friday 6 June, Amira spends five minutes sending Owen an instruction to move Kira's planning visit from 13 June to 9 June. That would displace another already promised visit. Owen spends ten minutes reading and flagging the conflict to Daniel, without changing either appointment.

Daniel spends 15 minutes checking the booking and returning the actual instruction: “Keep both existing appointments. I will speak to Kira to understand the request. Amira's context is welcome, but her message is not authorization to displace another customer.” Owen spends five minutes reading that answer.

Daniel and Kira then spend 15 minutes on a call. Kira declines a 9 June visit because she is unavailable. She explains that the immediate problem is uncertainty about preparation, not the visit date. She asks to retain 13 June and proposes a ten-minute clarification call on Tuesday 10 June at 11:00.

Daniel checks his availability during that call and personally accepts the proposed slot. No visit has been moved, and a customer's actual counterproposal has replaced the assumed need for urgency. Kira has not agreed to a new service package or faster digitization.

Daniel also spends ten minutes writing Amira a factual repair message:

“Kira has declined 9 June and kept the 13 June visit. We have agreed a ten-minute preparation call on 10 June at 11:00. Please send historical context to me under our handover arrangement. Owen will not act on a scheduling instruction from you. A concern about the delegation can go through Tessa's agreed route.”

Amira spends 15 minutes reading that message and sending a context note to Daniel instead of another scheduling instruction. Daniel spends five minutes reading it. Tessa spends ten minutes reviewing Daniel's factual bypass account and replying that the delegation remains unchanged. Daniel's 15-minute initial checking and reply allocation includes preparing that account and reading Tessa's response, as well as the answer to Owen.

Amira says in her note that she still dislikes being absent from operations meetings. Her response is not presented as complete acceptance of the succession. It establishes one actual use of the new advice route.

Deliver the agreed clarification and verify the limited result

The 10 June call lasts ten minutes for Daniel and Kira. Kira asks whether she needs a new folder index or only the box count and existing labels for the planning visit. Daniel answers that the count and existing labels are sufficient for this visit; no newly prepared folder index is required. Kira confirms that answers her preparation question. Daniel makes no promise about the later digitization schedule.

Owen spends ten minutes preparing for the 13 June visit, then conducts the agreed 30-minute planning visit with Kira. He spends five minutes recording its completion. Daniel spends five minutes reading the completion record. These are observed case events, not tasks marked complete merely because the scheduling issue was discussed.

On 16 June, Daniel spends 20 minutes preparing and sending the promised factual review request to Amira, Tessa and Owen, then reading their returned answers. That allocation includes the three recipients' replies being received, rather than counting only composition.

Each recipient spends five minutes reading and responding. Owen confirms he flagged the one conflicting instruction and delivered the original visit. Amira confirms she sent her subsequent context to Daniel, but still wants the meeting-attendance question considered. Tessa confirms no delegation change has been approved; any proposal about a continuing founder role needs the appropriate decision process.

Daniel's 15-minute closing coaching conversation with Suri examines those actual responses. The new route worked after a real breach, a customer was heard and the original visit occurred. The case does not establish that future bypasses have stopped, the relationship is repaired or an additional founder role is approved.

Include the receiving and review work in the account

The following ledger covers all described transition coordination, coaching, clarification and planning-visit work by the six named people. It excludes unrelated business operations and does not reconstruct the earlier board appointment process. The already approved appointment is a starting condition of this fictional case.

The total is 585 person-minutes against 660 allowed, leaving 75. The 45-minute joint conversation counts for four people, including Suri. The customer and staff receiving work is included. None of the remaining time automatically authorizes extra meetings or extends Amira's context window.

Keep coaching records distinct from governance records

In Coachful, Daniel can prepare an original worksheet about the next transition conversation and record an agreed action in the client goal activity. The organization's authorized system holds the operational handover and delegation records. A coaching worksheet does not amend those documents or prove that a board decision occurred.

Worksheet Coach review is private to the authorized coach team, not a delivered response to the client or board. In this case Suri's feedback occurs in the two counted individual coaching appointments. No extra written feedback event is silently assumed. If written comments are promised in another engagement, deliver them through the checked individual client conversation and include receiving time.

Unshared journal pages are not ordinary coach-readable notes; explicit client sharing through supported specialty flows can make particular pages available. Choose any sponsor update separately. Check automatic recap wording and audience before sending, including session-type overrides. A settings change cannot recall an already sent recap.

Use the Coachful features for preparation and agreed follow-through. For the earlier governing-group inquiry, see the succession reframing guide. This post-appointment record serves the different question of who actually does what after that decision.

Troubleshoot the handover

• The founder's advice keeps acting as a veto. Compare actual decisions with the delegation. Ask the proper authority to resolve the discrepancy rather than redefining an informal approval as a necessary polarity.
• A customer still calls the predecessor. Establish what the customer needs and what has already been promised. Contact preference is not authority to displace another commitment.
• The successor changes everything immediately. Ask which inherited obligation might be affected and who has checked it. Renewal does not eliminate existing responsibilities.
• The predecessor agrees in the meeting but bypasses later. Address the actual instruction and consequence. Preserve the event and use the agreed escalation route; do not infer a hidden psychological diagnosis.
• The overlap never ends. Review the actual remaining dependencies and ending condition. Continuing a historical-advice role requires a decision, scope and capacity, rather than an automatically renewed personal expectation.

Frequently asked questions

Are continuity and renewal always a polarity?

They can describe recurring interdependent needs, but test that framing against the work. A missing delegation, improper instruction or specific appointment still requires an authorized decision or response.

Does dialogue require agreement between predecessor and successor?

No. They can understand a concern and still disagree. Record the decision owner, actual answer and unresolved issue instead of using attendance or a polite response as evidence of consensus.

Does an advisory title preserve executive authority?

Do not assume it does. Check the actual appointment, governing documents and approved delegation. Define the contribution and information route through the appropriate process.

Is a hundred-day handover the best approach?

No optimal duration is established here. Choose review points around the actual role, decisions and obligations. Immediate operational responsibility can coexist with longer-term learning.

What counts as a completed succession outcome?

Name the observed event. In the fictional case, the bypass was flagged, the customer accepted a different support route, the original visit occurred and three actual review replies were received. Broader relationship and long-term transition outcomes remain unknown.