Executive Succession Polarities: A Dialogue Guide
Nour
Founder, Coachful
Executive succession polarities become useful when they change the question a leader asks. Instead of deciding whether the predecessor is obstructive or the successor is reckless, examine what each person wants to protect, which assumptions need evidence and who can authorize the next action.
Continuity and renewal can remain important together. A customer obligation, a delegated spending limit or a board resolution still needs a specific answer. This guide develops that distinction through a complete fictional service decision, including a mistake discovered during implementation. It focuses on reframing a contested proposal after succession, rather than selecting the next executive or designing the whole handover.
Understand the contribution of dialogic leadership
In his original article Dialogic Leadership, William Isaacs describes listening, respecting, suspending certainty and voicing. Listening seeks to understand another account rather than prepare a rebuttal. Respect explores why a view makes sense to its holder. Suspension makes thinking available for examination instead of suppressing it or presenting it as unquestionable. Voicing contributes a considered perspective.
These practices concern the quality of inquiry. They do not mean that everyone has equal authority over the eventual decision. The following questions and records are original coaching applications, not a validated succession assessment or a reproduction of Isaacs’ method.
A useful reframe changes something testable. “Owen dislikes my appointment” gives Priya little to investigate and risks confusing interpretation with fact. “Owen says one customer has a different agreed service route” identifies a document, a knowledgeable owner and a potential boundary on the proposal. Priya can investigate that claim while still challenging unnecessary approvals.
Dialogue also needs a stopping point. Once the relevant evidence and contributions are available, the decision owner decides, defers with a specific missing condition or declines the proposal. Repeating an inclusive conversation indefinitely can leave staff facing contradictory instructions.
Distinguish a polarity from a finite decision
Barry Johnson’s Polarity Management distinguishes ongoing, interdependent demands from problems to solve. Its public book preview offers two tests: whether the difficulty continues over time and whether the two sides depend on each other. Applied carefully, continuity and renewal may qualify: useful change depends on retained capabilities, while continuity can depend on adaptation.
That does not make every disagreement a polarity. Whether a current agreement includes a particular service is an evidence question. Whether the organization accepts a proposed amendment is a decision. Whether someone is authorized to approve it is a governance question. Calling these matters “balance” does not answer them.
For example, keeping an expired internal approval forever is not necessary merely because continuity matters. Equally, changing a current customer promise without the required authorization is not justified by renewal. The ongoing needs help leaders design options; the finite obligations determine what those options can actually include.
Use the polarity management guide for the broader distinction. Here the practical test is whether the framing produces better evidence and a clearer decision, rather than a symmetrical diagram.
Explore four perspectives without assigning people to sides
Invite each participant to consider all four perspectives. The outgoing leader may want a substantial change; the incoming executive may be the person protecting a valuable practice. Avoid turning position, age or tenure into a personality explanation.
| Perspective | Useful inquiry | Possible evidence |
|---|---|---|
| Value of continuity | Which existing commitment or capability must the proposal preserve? | A current service agreement and the expertise needed to deliver it. |
| Cost of continuity without review | Which inherited step continues after its purpose has disappeared? | Two approvals checking the same information without a separate control function. |
| Value of renewal | What useful difference would the proposed change make? | A defined route that removes an unnecessary handoff. |
| Cost of change without context | What dependency could the proposal overlook? | A customer exception missing from the ordinary routing screen. |
These are candidate contributions, not findings. A familiar process may contain a control nobody initially explains. A long-standing promise may have changed. Ask for the source and its current applicability before putting either claim into a board recommendation.
Establish the fictional engagement and decision authority
All people, company records, dates and results below are invented teaching examples. Priya became chief executive of Northbridge Service Systems on 1 October 2026. Owen, the previous executive, now advises on historical customer arrangements. He has no executive approval or veto under his written advisory terms.
Priya proposes removing a second supervisor approval from routine requests. Owen says the change could break a promise to Lark Manufacturing. Board chair Dina asks for a decision brief rather than an account of who is being difficult.
Priya’s coach Jules provides three individual sessions on 4 November, 18 November and 2 December. Jules helps Priya examine assumptions and prepare her contribution. Priya leads the company discussions herself. Jules is not assessing Owen, advising on the customer agreement or determining whether Priya should have been appointed.
Before work begins, Priya, Jules and Dina agree the sponsor receives session attendance dates and a purpose statement Priya approves. Individual preparation and session content stay outside that routine report, subject to the discussed confidentiality limits. Jules has no separate engagement with Owen. Any request to change this reporting arrangement returns to all relevant parties before disclosure.
The current ICF Code of Ethics addresses agreements, information exchange, conflicts and disclosure of different professional roles. A sponsor’s payment does not settle what information the coach may share.
Company secretary Noor confirms the actual internal arrangement: the board has reserved this transition pilot for its decision; Priya implements only the approved scope. Changes to the Lark commitment require a separate proposal, qualified review and the necessary customer agreement. These are fictional company arrangements, not universal rules for every board.
Turn the initial disagreement into questions that can be checked
In the first session, Priya notices that she has combined three claims: Owen objects to the route, the route contains duplication, and Owen therefore opposes her leadership. Only the first is directly supported by the exchange she describes. Jules asks what would distinguish a necessary control from an inherited preference.
Priya prepares this short record:
Observation: Owen said, “Lark was promised a different route.” He did not identify the current document in that meeting.
My interpretation: He wants the old process retained because it was his process.
Alternative explanation: The proposed design may omit a current customer obligation.
Check: Ask account owner Asha and qualified contract adviser Morgan to establish what currently applies. Ask operations manager Ben what each approval actually checks.
My contribution: I still propose removing genuinely duplicate work. I will distinguish that proposal from changing a customer commitment.
Priya sends the evidence requests through company work email. The company’s controlled customer archive remains the source for agreements. She does not upload the agreement or customer identifiers into her coaching worksheet. Jules receives only the permitted summary needed for coaching.
The preparation improves the question without deciding it. Owen’s concern could still be mistaken. Priya has agreed to check its substance, not to accept every historical recollection as binding.
Use the actual dialogue to revise both interpretations
On 11 November, Priya meets Owen, Asha and Ben. She opens with the decision question and asks Owen to explain the particular dependency before discussing the proposed replacement route.
Owen: Lark has a named technical reviewer and a two-hour acknowledgment route. I am worried the ordinary queue would replace that.
Priya: I heard your concern as opposition to removing approvals. I withdraw that interpretation. Which part requires two supervisors?
Owen: I do not know whether both signatures are required. My concern is the technical route.
Ben: The first supervisor classifies the request. The second repeats an identity check. The technical reviewer is a different role.
Priya: Then we need to verify those functions separately. I want less duplication while keeping any current special route intact.
Priya has listened for the specific concern and voiced her proposal clearly. Owen separates his knowledge from a claim he cannot support. The exchange does not require Owen to endorse Priya personally, disclose feelings about retirement or perform a public transfer of authority.
When Ben asks Owen which route to use pending the decision, Owen redirects him to Priya. Priya confirms the existing route remains in force until the authorized pilot starts. This small operational answer matters more than a general statement that everyone now trusts the succession.
Replace the preliminary register with verified findings
By 16 November, the named owners return these fictional findings through the company’s controlled records:
| Question | Verified result | Decision consequence |
|---|---|---|
| Does Lark still have a special route? | Asha and Morgan confirm the applicable signed schedule provides the named technical reviewer and two-hour acknowledgment through 31 March 2027. | The current pilot must preserve that route. A different arrangement remains a separate matter. |
| Does that schedule require both supervisor signatures? | Morgan confirms the second internal signature is not specified in the schedule. Ben verifies it repeats the identity check, with no separate control function identified in the reviewed process. | Removing it may be considered within a defined internal scope, while retaining classification and technical review. |
| Can the current routing screen identify every exception? | Ben finds the customer exception field is not consistently populated. | A blank field cannot prove a request is ordinary. Verification against the controlled customer record is needed. |
| Has the proposed improvement been demonstrated? | No live test has taken place and no reliable comparative timing baseline exists. | Describe removal of a step as a design change, not a proven service or financial benefit. |
The contract adviser establishes the fictional document’s meaning; Jules does not. The operations finding is also limited to the process reviewed. If another control owner identifies a distinct purpose, the recommendation must return for examination.
For governance context, the Financial Reporting Council’s UK Corporate Governance Code 2024 addresses orderly succession and clear written responsibilities. Its actual application concerns specified UK listing categories and a comply-or-explain framework, rather than every private company worldwide. The Northbridge example uses its own confirmed arrangements. A coaching conversation does not establish legal compliance.
Produce a board brief with an answerable request
In the second session on 18 November, Jules asks Priya to remove statements about Owen’s motives from her draft. Priya replaces “resistance to transformation” with the verified customer dependency and the remaining design risk. Her company brief reads:
Decision requested: Approve a limited routine-request pilot from 23 to 27 November. Remove only the second duplicate identity approval. Retain first-supervisor classification and the existing technical review.
Excluded scope: No change to Lark’s special route, acknowledgment commitment or customer terms. Requests with uncertain status use the existing route while Asha checks the controlled customer record.
Alternatives: Keep all current steps, which avoids a transition now but retains the duplicate check; run the limited pilot with verified classification; or redesign all routes later after separate customer and authority questions are resolved.
Recommendation: Choose the limited pilot. Ben owns implementation and checks every request before release. Use existing staff time; no new purchase or financial saving is assumed.
Stop and restart: Any incorrect classification pauses the pilot. Ben documents the cause and corrective checks. Only Priya may authorize a restart within this scope after reviewing that evidence.
Review: Ben reports actual request counts, routing errors and unresolved delays on 30 November. Expansion needs a new decision; completing this pilot does not authorize rollout.
On 19 November the board approves this scope, and Noor records the resolution. Priya sends Ben the approved instruction by work email; Ben acknowledges it and briefs the service team before 23 November. Owen receives the approved operational summary as adviser, without becoming an additional approver.
The decision is complete at this stage. Delivery and benefit are not. A useful brief distinguishes its chosen action from the evidence that will later determine whether to retain, revise or stop it.
Keep the failed classification in the implementation record
On 23 November, a Lark request has a blank exception field. A team member treats it as routine despite the instruction to verify status. Ben’s required pre-release check catches the mistake, holds the request and directs it through the existing Lark route. The acknowledgment remains within the fictional two-hour commitment. The record still counts this as a classification error.
Priya pauses the pilot under the approved rule. Ben finds that the team instruction described the verification step but the routing checklist did not require a recorded source. He changes the checklist to require a customer-record reference and a confirmed category; uncertain status explicitly goes to the existing route.
On 24 November the team tests six fabricated requests: four ordinary, one Lark and one with unresolved status. All six follow the revised rules. Ben records the completed outputs, including the unresolved request held for Asha rather than guessed ordinary. Priya reviews the evidence and authorizes restart within the original end date.
These six are training cases, not six additional live requests. By 27 November, the live pilot contains twelve requests in total: ten ordinary and two Lark, including the initial misclassification. Both Lark requests use their existing special route. All ten ordinary requests proceed without the second identity approval.
Eight ordinary requests finish without a recorded delay; two wait for missing technical information. The team has removed one handoff, but those delays remain. With no reliable baseline or comparable control group, Priya does not report a percentage improvement, cash saving or causal benefit from coaching.
Close the finite choice and retain the ongoing questions
Ben’s 30 November report retains the error, pause, corrected training cases and twelve-request denominator. Priya decides against immediate expansion. The board agrees to keep the existing wider process while Ben develops a separate controlled proposal using the revised classification check.
Priya sends this closing instruction to Ben and Asha through company work email, with Dina and Owen copied on the permitted operational record:
The 23–27 November pilot has ended. Do not extend its scope. The initial Lark misclassification was caught before release and is retained as an error. The revised check routed six fabricated tests correctly. Across twelve live requests, ten ordinary requests omitted the second identity approval and both Lark requests retained their special route. Two ordinary requests still waited for technical information.
The wider route remains unchanged. Ben owns the next proposal, including verification evidence and unresolved delays. Asha owns any separate customer discussion. No change to Lark’s terms is approved or agreed. Please acknowledge this instruction in this email thread.
Ben and Asha acknowledge the instruction that day. No customer amendment has been proposed or accepted in this case. In the final coaching session on 2 December, Priya identifies her changed practice: ask what an objection protects, then distinguish the evidence and authority needed for each part of the proposal. Jules and Priya close the three-session engagement without claiming a successful rollout.
Continuity and renewal remain relevant to the next proposal. The failed classification does not prove all change is unsafe, and the removed handoff does not prove every inherited check is redundant.
Use Coachful for the leader’s preparation and review
Coachful is our #1 recommendation for organizing this coaching work because a leader’s preparation, agreed actions and later reflection can stay connected across sessions. It supports the coaching process; the company retains authoritative contracts, board decisions and operating records.
- Send a focused worksheet. Build a form or worksheet resource with the observation, interpretation, alternative explanation and evidence-owner prompts. Deliver it directly to the intended client. Check its access and avoid a broadly shared resource folder for restricted preparation.
- Name the submission route. In this example Priya sends her permitted summary through her individual private Coachful conversation with Jules before each scheduled session. Jules is the sole authorized coaching staff member and reviews it in that session. The service includes no additional between-session advisory review.
- Agree concrete actions. Record the actions Priya accepts, such as requesting the operations check or preparing the board brief. A checked task records follow-through, not verified legal authority or board approval.
- Review what changed. Connect reflection to the actual revised question and company outcome. Priya’s own summary can say the pilot stopped without copying the confidential customer schedule into her coaching workspace.
The demo form builder illustrates structured preparation prompts. Its sample wellness content is not a succession assessment. The goal view below illustrates linked actions and reflection, not Northbridge’s pilot results.
Keep sponsor reporting deliberate. Priya approves the separate purpose statement before Jules sends it to Dina by their agreed work-email route. Private preparation is not automatically a board paper. Explore Coachful’s features for client resources and follow-through, and the succession handover guide for broader role and transition planning.
Adapt the process and troubleshoot predictable failures
Use this sequence for your next contested succession proposal: define the finite decision; confirm who decides; invite the four perspectives; separate observations from interpretations; assign missing evidence to competent owners; compare feasible options; secure the actual decision; communicate the instruction; and review what happened against its stated limits.
A compact preparation template is: “I observed __. I interpreted it as __. Another possible explanation is __. The evidence owner is __. The decision belongs to __. I propose __ within __. The remaining condition is __. We will check the actual result on __.” Complete the blanks with sources and named people before treating it as ready.
If the outgoing leader repeatedly gives operational instructions, return to the confirmed role and escalation route. Listening to their expertise does not require staff to follow an unauthorized instruction. Record and address the actual conflicting message through management.
If the successor calls every concern resistance, ask for the specific observation and what evidence might change that interpretation. If a concern is verified, change the proposal visibly rather than merely thanking the contributor.
If a clear duty is being presented as a polarity, stop the balancing exercise. For example, a verified required approval cannot be replaced with equal airtime for compliance and noncompliance. Obtain the necessary qualified advice and decision.
If the conversation becomes personal, ask whether participants want to explore the experience and whether the current setting is appropriate. Do not diagnose grief or demand emotional disclosure. A separate service, different facilitator or revised engagement may be needed.
If the team reports agreement without action, ask for the actual instruction, recipient acknowledgment and decision record. “We support continuity and renewal” does not tell a service operator which route to use tomorrow.
Frequently asked questions
What are executive succession polarities?
They are potentially ongoing, interdependent needs arising during succession, such as retaining valuable capabilities while adapting the organization. Test the relationship in the actual setting. A particular appointment, contract term or authorization remains a specific decision or evidence question.
Does dialogic leadership require consensus?
No. Participants can understand one another more accurately and still prefer different options. Confirm who owns the decision, which contributions they need and how the final instruction will be communicated. Dialogue should inform that responsibility rather than obscure it.
How can a coach support both predecessor and successor?
Only through an explicitly agreed service with clear roles, information boundaries and conflict handling. This example deliberately coaches Priya alone. Coaching both individuals, facilitating a joint meeting or assessing candidates introduces different responsibilities that should be agreed before accepting the work.
Can a four-perspective worksheet assess leadership capability?
It can support preparation and inquiry, but the original worksheet here is not a validated selection or performance instrument. Appointment and compensation decisions need their own appropriate criteria, evidence, authority and professional competence.
What counts as a completed outcome?
A verified decision, communicated instruction and observed review can complete a bounded piece of work even when wider change remains pending. In the fictional case, the pilot ends, its error stays visible and expansion is not approved. That is more informative than claiming the succession tension has been permanently solved.
