Frame a Post-Merger Governance Discussion Around Decisions

Post merger leaders often request integration support before anyone has agreed how a decision moves from a workstream to an executive sponsor. Progress reports sometimes show green marks across every function while important choices sit unresolved. A business development director earns a useful first meeting by treating governance as a working system for decisions. Start with choices, owners, evidence, and the route for resolving conflict. Do not start by presenting a large integration program.

An executive might say, “Our teams are busy, yet nothing seems to move.” Resist the urge to label the situation a communication problem. Ask for one decision whose delay has caused a real consequence. The consequence might involve a customer proposal, an employee announcement, a systems change, or a site plan. Then ask who prepared options, who must approve the choice, and what information each person asked to see. Those answers reveal whether the obstacle sits in ownership, meeting design, missing facts, or a sponsor disagreement.

Ask about the point when an issue changes hands. A workstream lead might select between two reporting structures, then learn human resources expects a different executive to decide. A regional leader might agree to a customer transition, then legal asks for review after sales has promised a date. Each handoff exposes a question: who has authority, what is the decision, and what record shows the decision? A calendar full of status meetings will not answer those questions.

In a fictional practice meeting, integration sponsor Elena says, “Every workstream sends updates, yet the combined company still feels stuck.” Director Marcus replies, “Please choose one decision from this week where progress stopped.” Elena names the customer account model. Finance wants accounts grouped by legal entity. Sales wants a view by buying group. Operations needs a model for service routing. Marcus asks, “Who has authority to select the model, and what would each owner need before making a choice?” Elena pauses. Sales believes the commercial chief owns the question. Finance believes the chief operating officer owns part of the answer. No shared record identifies a final owner.

Marcus does not claim an answer. He asks what happens if no choice occurs before the next billing cycle. Elena says account teams will use separate customer lists, and service staff will receive unclear requests. Marcus follows with, “Who feels the impact first, and who should describe the evidence in a decision session?” Elena names the billing lead, a sales operations manager, and the service leader. Their names become more useful than a vague promise to involve all stakeholders.

The next conversation should test whether an executive sponsor will convene the needed people. Ask who would open the session, who would prepare options, and who would record a decision. Learn whether prior meetings ended with a stated owner and due date or with a request for more socialization. Socialization has a place when a leader needs input. Yet a decision meeting needs a different outcome: a named owner accepting a choice, a request for more evidence, or an escalation.

Offer a narrow working session only after the buyer describes a real choice. In the fictional situation, Marcus proposes a ninety minute session focused on the account model. The service leader brings examples of misrouted requests. The billing lead brings the current account fields. Sales operations brings a view of affected accounts. The sponsor brings the decision question in one sentence: “Which account model will govern customer ownership for the first combined billing cycle?” A short agenda leaves room for the work. First, confirm the decision. Next, compare the available choices against customer service, billing, and ownership needs. Last, record the owner, evidence gap, and next date.

Do not promise a completed operating model from one session. State the output plainly. The group will produce a decision record and identify evidence missing before a final selection. This boundary protects both sides from an early claim about scope. An advisory team might later help define a broader governance structure, but the prospect first needs confidence in a small decision process.

Here is a fictional decision record for practice. The title reads “Customer account ownership for first combined billing cycle.” The decision owner is the chief operating officer. Contributors include sales operations, billing, service, and finance. The decision date is October 14. Evidence needed includes a list of accounts with conflicting ownership and two examples of service routing. The record also names a sponsor who will resolve disagreement if contributors reach no shared recommendation. Such a record does not solve a dispute. The record gives the dispute a home and a deadline.

Listen for a buyer who asks for a governance model before naming decisions. A gentle redirect helps. Say, “A model will be easier to assess once we look at a few choices already under pressure. Which choice should receive attention first?” This question keeps discovery concrete. Also listen for people who want a director to arbitrate executive conflict. The director should identify the conflict, not take authority away from the client. Ask which sponsor owns resolution and whether a meeting has been scheduled for the choice.

Some decisions affect employees before leaders see a clear operational impact. Reporting lines, role titles, location changes, and manager assignments invite urgency. Ask what employees have heard, what leaders are prepared to confirm, and who approves the message. Avoid offering employment advice. Focus on the decision path and on the people authorized to provide policy or legal guidance. A well timed message needs a decided owner and approved facts, not a polished script built around assumptions.

In a fictional follow up, Elena says the commercial chief and chief operating officer both want input before choosing the account model. Marcus asks whether either leader has final authority or whether a sponsor must assign one. Elena decides to ask the chief executive's office for a written designation. Marcus suggests a short note: the decision question, the owners who disagree, the date customer billing needs an answer, and the consequence of delay. The note is an example of preparation, not a substitute for the executive's decision.

For a practice exercise, choose a fictional integration issue such as combining two customer intake processes. Write the decision question without a solution inside. Then write the names or roles of the decision owner, contributors, evidence holders, and escalation sponsor. Add one consequence tied to a date. Read the question aloud. If a colleague cannot tell what choice belongs to whom, revise the wording.

Use the exercise in a roleplay. One person plays an integration sponsor who asks for broad help. Another person plays the director. The director asks for a delayed decision, follows the trail of authority, and proposes one focused session. End with a real preparation move from the practice situation. For the fictional intake issue, send the sponsor a blank decision record with “customer intake process for November 3” in the title and ask the service lead to enter two recent intake errors before the session.