Dialogic Leadership in Mergers: A Handover Agreement
Nour
Founder, Coachful
Dialogic leadership in mergers helps people examine how their work should fit together after a transaction. A useful conversation moves beyond “our culture versus theirs” to a specific decision: what must be shared, what local judgment still matters, who has authority and how a failed handover will be repaired.
The result should be more than an integration slogan. People need an operating agreement they can use when a customer asks for work, a receiving team lacks information or a promised date has no authorized owner.
This guide develops one post-closing handover case through two trials. It preserves a broken customer promise, a commercial refusal and a later routing error. A clearer process emerges without claiming that dialogue has merged two cultures or delivered financial synergies.
Establish the transaction stage and actual mandate
Before closing, the parties remain subject to applicable information-sharing, competition and other restrictions. The FTC’s 2018 primary pre-merger guidance, within its United States context, explains risks from inappropriate exchange of competitively sensitive information and coordination. A workshop invitation does not authorize operational integration.
Qualified legal and governance owners should define the actual boundaries. Do not infer that a proposed transaction allows customer records, prices, staff information or systems to be combined. Closing also does not remove every contractual, privacy or employment obligation.
Employment consultation has its own requirements. For example, Acas guidance on a TUPE transfer says employers must allow enough time to inform and fully consult before the transfer. Whether TUPE applies depends on the actual transaction. A coaching workshop is not a substitute for the relevant process.
The worked case below occurs after closing. The responsible owners have authorized the information and bounded workflow being considered. Its council can recommend a process, while named service and commercial owners make the actual decisions. That distinction prevents a good conversation from becoming an unauthorized instruction.
Use dialogue to examine assumptions, not erase disagreement
William Isaacs describes listening, respecting, suspending certainty and voicing as practices of dialogic leadership. Suspending a view means making its reasoning examinable, rather than concealing it or insisting that it must be right. The leader participates in that scrutiny too.
For a merger conversation, listening can mean asking what the receiving team actually needs before judging a regional practice. Respect can mean taking the existing expertise seriously without endorsing every old procedure. Voicing includes saying clearly that a customer promise cannot be met. It need not produce an agreeable answer.
The two organizations are not permanent opposing camps. A person from either business may want consistent records, useful local discretion or clearer commercial limits. Labels such as “acquirer control” and “acquired-company resistance” can conceal the practical question.
Barry Johnson’s polarity lens concerns ongoing, interdependent needs. The question is whether attending only to one need will eventually undermine useful work. That differs from a finite choice of system, a broken access control or a condition that must be satisfied. See the polarity management guide for the wider approach; the records here are original applications.
Make four possible integration tensions useful
| Needs to examine | What both may contribute | Question that makes it practical |
|---|---|---|
| Common standards and local knowledge | Consistent essential information and awareness of the actual customer context | Which fields must be shared, and who can judge a genuine exception? |
| Integration and service continuity | A workable future process while current promises remain owned | Who answers a customer while the new route is being tested? |
| Existing expertise and future capability | Retained knowledge and deliberate learning for changed work | What must people learn, and what should the new process learn from them? |
| Cost discipline and adequate capacity | Attention to resources without hiding transition and review effort | Which work stops or waits when a new approval step is added? |
These are candidates to test, not four universal merger dimensions. Someone may point out that an apparent cultural disagreement is an unclear service contract. That correction should change the agenda.
A useful signal is observable. “Protect local knowledge” becomes meaningful when a common form loses a customer-specific condition. “Maintain standards” becomes meaningful when a receiving team starts work without a verified commitment. Respond to the event, rather than scoring the employee’s attitude toward integration.
Worked case: a shared brief with a disputed approval step
All organizations, people, requests and events in this case are fictional. Alder and Beacon have completed a business-services merger. Ines coordinates integration. Ravi sends customer requests from an account team, Lena leads the receiving service team, Kit owns service authority and Ola owns commercial exceptions. These five people form the bounded working council.
The proposed route combines a common brief with Kit’s central check on every handover. Ravi argues that the former local route was quicker. Lena says that some old requests lacked a verified commitment, so her team could not tell whether it was assessing an idea or delivering a promise.
In individual coaching on 4 November, Ines initially describes this as a conflict between speed and bureaucracy. Her coach, Noah, asks what the central check is supposed to establish. Ines cannot answer precisely. She decides to bring an actual routine request and an exception to the council, with customer identities minimized and permitted information in the approved company system.
1. Give the meeting a decision it can actually make
Ines sends the other four participants the proposed brief and a sixty-minute agenda for 6 November. They can add comments to the existing company handover-register discussion before the meeting. Ines will record which suggestions are accepted, declined or require an owner’s decision. Private employment concerns use the existing HR route, not this shared customer-work record.
The agenda gives five minutes to mandate and audience, fifteen to sending and receiving examples, fifteen to routine and exception routes, fifteen to drafting and testing the brief, and ten to decisions, owners and communication. That totals sixty minutes.
Kit confirms that he can authorize this service-work trial. Ola confirms that commercial changes remain with her. Neither the council nor Ines can amend employment terms, promise customer concessions or authorize a systems migration through this meeting.
Ravi: I hear the central step as losing the judgment we used to exercise locally.
Lena: I need to know which promise is real. A requested date and an agreed date are not the same.
Ines: I assumed one review would solve the information problem. Let us separate the shared information from who must approve the work.
Kit: For the first ten handovers, I will check each brief centrally so we can see what is missing. We will then review whether that step is needed for routine work.
Kit explicitly accepts the temporary checking work and dates the review for 16 November. It is a trial condition, not evidence that all later requests need his approval.
2. Complete the operating agreement before trying it
| Field | Agreed first-trial arrangement |
|---|---|
| Scope | The next ten relevant administrative service handovers received from 9 to 13 November |
| Required brief | Task, permitted supporting information, verified existing commitment, requested date, sending owner and proposed work estimate |
| Receipt | Lena acknowledges arrival in the company register; this is not approval or a delivery promise |
| Assessment | Lena checks completeness, work estimate and whether the request fits the routine category |
| Routine boundary | At most two service hours, unchanged agreed scope and commercial terms, with capacity accepted by Lena |
| Exceptions | More than two hours or changed scope, price or terms go to Ola; unresolved authority or capacity goes to Kit as appropriate |
| Trial check | Kit additionally checks every brief before work is committed during this first ten-request trial |
| Delivery commitment | Lena accepts an achievable date; Ravi obtains any necessary customer acceptance before reporting an agreed date |
| Record and review | Retain missing information, wrong routes, changed promises and open work for the 16 November review |
Kit verifies the routine delegation in writing. Ola confirms the exception boundary. Ravi and Lena acknowledge the status meanings and accept their respective work. Ines saves the authorized version in the company register and tells the affected senders which version to use.
They have standardized the minimum brief. They have not decided that all information belongs in one system, that local teams may invent their own approval thresholds or that all customers have accepted changed terms.
Complete the failed customer promise, not just the form
Ten handovers enter the first trial. Seven are within the routine category and three are exceptions. Eight of the ten contain all required fields initially. H07 lacks the verified commitment; H10 lacks the requested date. Ravi supplies both missing fields by 12 November, so all ten briefs become complete, while some decisions remain open.
H03 exposes a different failure. It is a complete routine request for ninety minutes of work. Lena acknowledges receipt on 9 November. Ravi treats that acknowledgment as approval and tells the customer the work will arrive on 12 November, before Lena accepts a delivery date.
Kit’s central check occurs on 11 November. Lena can offer 13 November but cannot meet the date Ravi promised. The brief was complete; the promise still lacked authority. Calling H03 a documentation success would miss the actual customer problem.
Ravi calls the customer on 11 November, acknowledges his mistake and sends the correction through their existing customer email thread:
“I treated our receipt acknowledgment as a delivery commitment and gave you 12 November too soon. I am sorry. Lena has now accepted delivery on 13 November. Please confirm whether that revised date works for you; I will not describe it as agreed until you do.”
The customer replies on 11 November that the delay is inconvenient but accepts 13 November. Lena completes the work that day, and the customer acknowledges receipt on 16 November. The record retains the original promise, one-day delay, apology, accepted revision and actual delivery. The later acceptance does not make the original promise accurate.
Ravi and Lena add a visible distinction to the register: received; ready for assessment; scope authorized; delivery date accepted. These are separate fields, not a single “approved” badge. They also agree that the customer-facing sender must check the last field before communicating a commitment.
Read the first trial with complete denominators
At the 16 November review, the ten requests have the following observed positions:
| Requests | Category | Observed position |
|---|---|---|
| H01–H05 | Five routine requests | Delivered; H03 includes the corrected late promise and receipt |
| H06–H07 | Two routine requests | Lena has accepted future delivery dates; work is not yet delivered |
| H08 | Exception exceeding two hours | Ola authorized the revised scope on 13 November; customer accepted the terms and Lena’s 20 November date that day; delivery remains future at this review |
| H09 | Exception requesting a concession | Ola declined the concession on 13 November; Ravi communicated it and the customer declined to proceed |
| H10 | Exception awaiting commercial decision | Brief repaired; Ola has accepted a 19 November review, but no approval or delivery promise exists |
Five delivered, two routine bookings, one approved and booked exception, one declined request and one pending decision total ten. Eight initially complete briefs become ten after repair. Neither number means ten successful deliveries or that integration is complete.
H08’s eventual delivery and H10’s decision are not reported as observed at the 16 November review. This time boundary matters even when you later learn more. A historical review should show what the team knew then.
The common fields helped Lena assess the work. The universal central check also created a queue: four of the seven routine requests waited more than one working day for Kit’s check after Lena had enough information to assess them. That is an observed trial condition, not proof that central oversight is always wasteful.
Ravi asks to restore the entire old local process. Lena rejects losing the verified-commitment field. Their preferences still differ, but the evidence supports a narrower revision: preserve the shared brief and use the verified delegation for routine work.
Authorize a revision and test the exception boundary
On 17 November, Kit authorizes a second trial for the next four relevant requests from 18 to 20 November. Routine work no longer needs his duplicate check. Lena can commit within the verified two-hour, unchanged-terms boundary when she has capacity. Ola’s exception role and the shared fields remain.
Kit approves the exact revised wording. Ola confirms her part; Ravi and Lena acknowledge the new route. Ines updates the version in the register and sends the specific change to affected senders and receivers. A verbal impression that “local authority is back” would be too broad.
Two routine requests, R01 and R02, follow the new route and are delivered by 20 November. R03 arrives marked routine, but Lena’s assessment shows three hours of work. She records the corrected estimate and refers it to Ola before starting or accepting a delivery date. The classification error remains visible.
The fourth request, R04, is correctly identified as an exception from the start. It needs information about proposed terms before Ola can decide. At the 24 November review, both R03 and R04 remain without final commercial decisions. Ola acknowledges their status and accepts a 26 November review after the required information is obtained. Ravi informs both customers that a date is not yet committed.
The four-request result is therefore two delivered and two still awaiting exception decisions. Correcting R03’s route is useful, but it is not a third delivery or proof that all senders understand the boundary. The second trial has a different case mix from the first, so its results should remain separate.
At the 24 November review, Kit retains the revised route only for this defined request class and asks for a short worked example on the two-hour boundary before considering a wider rollout. Ines supplies a one-hour unchanged-scope example and a three-hour exception example; Kit checks the distinction. Wider rollout remains unapproved. Future exception decisions and any lasting change in routing accuracy are unknown.
Count effort without inventing synergy savings
The first ten handovers record 110 minutes of sending work, ninety minutes of receiving assessment and sixty minutes of Kit’s additional checks. That is 260 staff-minutes. It excludes delivery work and the council meeting.
The second four record forty minutes of sending work, thirty-five minutes of receiving assessment and fifteen minutes of commercial exception assessment so far. That is ninety minutes. Future work on R03 and R04 is still owed, so this is not the final effort for the four cases.
The sixty-minute first council meeting alone uses 5 × 60 = 300 staff-minutes. Those minutes cannot disappear from a transition-cost discussion simply because the meeting felt productive. Nor can 260 minutes for ten requests and ninety minutes so far for four different requests establish an efficiency improvement.
A credible later comparison would define similar work, include missing-information repair and all completed exception work, and keep service quality in view. This case makes no causal merger ROI, cost-saving, customer-retention or culture-change claim. Its narrower evidence is an observed problem, an authorized process revision and a further error caught before a new promise.
Use a practical operating-record template
- Define the work and scope. Name the request class, transaction stage and current responsibility.
- Separate information from authority. State the required fields and who can approve scope, terms, capacity and dates.
- Define statuses in usable words. Say what receipt, assessment and acceptance do and do not establish.
- Provide an actual contribution route. Explain who sees comments, who responds and where sensitive concerns belong.
- Record the trial and its costs. Keep missing fields, wrong classifications, refusals and unresolved work.
- Authorize the next version. Name the actual approver, accepted owners, communication and conditions for further review.
A short register entry can use these fields: request; existing commitment; requested date; sending owner; required information; assessment owner; scope authority; accepted delivery date; customer response; issue; actual resolution; pending action. This is an original working record, not a legally binding merger covenant or a complete integration plan.
For H03, a completed entry preserves “12 November promised without acceptance,” “customer accepted 13 November after apology,” “delivered 13 November” and “receipt acknowledged 16 November.” Replacing those facts with “handover improved” would remove the lesson the team needs.
HSE’s Management Standards guidance on change emphasizes timely information, opportunities to influence proposals, likely job impacts, timetables and support. In its workplace-stress context, that supports explaining the actual workflow change. It does not mean a handover meeting satisfies every employment duty.
Support the leader’s preparation in Coachful
Coachful is our #1 recommendation for organizing the individual leader’s coaching preparation and follow-through around this integration question. Keep authoritative commercial approvals, customer records, employment matters and technical documents in the organization’s approved systems.
Noah is Ines’s sole coach in a private coaching workspace. He assigns an original worksheet through Clients > Ines > Worksheets & resources > Assign. It asks what she observed, what she inferred, which decision is open, who holds authority and what would contradict her preferred explanation. The pictured wellness question is only a demonstration of the builder.
Ordinary dated tasks can track Ines’s preparation and review. Their status should distinguish a recommendation, an actual authorization and an open commercial decision. A coaching task does not make Kit’s approval exist or allow Noah to inspect the company’s customer register.
They agree one brief clarification in one-to-one Messages by 5 November at 12:00, Europe/London, with Noah’s response due at 17:00. Ines asks at 10:00 whether the council’s support alone can authorize the trial. Noah replies at 14:00 that she should establish the relevant owners’ actual decisions and communicate their scope. He promises no ongoing operational monitoring or legal review.
Unshared journal and takeaway pages remain private to the client. Where enabled, Share with coach lets the client deliberately share an individual page with the coach. Keep sensitive personal words unshared. Ines deliberately shares a permitted summary. For any summarized session, Noah checks the automatic recap default, Approve before sending and session-type overrides before use, then reviews held material against their agreed audience. Neither merger staff nor a sponsor automatically receives her private coaching reflections.
The related M&A oversight guide covers board evidence and escalation. This guide’s distinct focus is the operational handover. Explore Coachful’s features for the preparation and reflection that support it.
Frequently asked questions
Does dialogic leadership mean preserving every legacy practice?
No. It invites people to examine the purpose and consequences of a practice. Useful local knowledge can change the proposed standard, while an unclear or unsuitable old route can still be replaced through the appropriate decision process.
Is integration always a balance between central and local control?
No. Some decisions are finite choices or requirements to meet. A polarity lens helps where recurring interdependent needs actually matter. The case retains common information and verified local delegation, while exceptions keep their authorized route.
Can we start coordinating before the merger closes?
Only within the actual legal and governance boundaries established for the transaction. Pre-closing planning is not permission for unrestricted information exchange or operational coordination. Obtain appropriate guidance for the specific circumstances.
How can we tell whether the operating agreement works?
Follow real requests through information, assessment, authority, customer communication and delivery. Include delays, corrections, refusals and work still pending. A complete form or a positive workshop response is not enough.
What should remain outside the coaching record?
Keep restricted customer, transaction, employment and technical records in their approved systems. A leader can share a permitted minimized account of their own preparation and decisions. The coach’s role and access should remain explicit.
