The Deal Closed. The Operating Model Didn’t
Leaders often finalize the economics of a deal before defining reporting lines, decision rights, governance, and process ownership, and that is where value starts leaking.
A surprising number of mergers are approved with more precision on the synergy slide than on the way the business will actually operate on Monday morning.
Leaders can usually tell you the deal multiple, the target synergies, the headcount assumptions, and the investor narrative. But ask who owns customer pricing decisions in the combined company, who resolves cross-site quality disputes, how capital requests will be prioritized, or which processes will be standardized versus left local, and the room gets vague fast.
This is not a cosmetic issue. It is the difference between a combined business that moves with discipline and one that spends 12 months in escalation, duplication, and internal friction. McKinsey says companies that effectively implement the combined operating model post-merger are more likely to meet or exceed cost and revenue synergy targets. PwC similarly reports that successful integrations were more likely to have planned the long-term operating model during deal screening.
Deals do not create operating discipline. They expose whether it was ever there.
The real post-merger risk is not synergy modeling. It is operating ambiguity.
Most leaders treat operating model design as something that can be sorted out after close. That is backwards.
The operating model is how the company converts strategic intent into execution. It defines reporting lines, decision rights, governance forums, process ownership, escalation paths, and the degree of standardization across functions and sites. McKinsey explicitly warns that operating model design in mergers requires more than “boxes and lines” and must address structure, process, and people.
Why this matters is simple. When these choices are left unresolved, the combined business defaults to politics. Legacy leaders protect their turf. Teams duplicate work because they do not trust shared processes. Functional decisions stall because no one knows whose approval counts. Local managers fill the vacuum with workarounds.
Synergy gets delayed not because the math was wrong, but because the business lacks a mechanism to act on the math.
What to do: move operating model design from integration clean-up to pre-close decision architecture. Before Day 1, define the minimum non-negotiables for how the business will run. Not every detail, but the key rules of the road.
Boxes and lines are the visible symptom. Decision rights are the actual system.
A merged org chart may look clean and still perform badly.
That is because the org chart answers only one question: who reports to whom? It does not answer the harder questions that actually drive daily execution. Who owns the customer? Who has authority over pricing exceptions? Who decides which ERP instance wins? Who sets quality policy for all sites? Who arbitrates supply allocation when demand exceeds capacity? Who can stop a product launch? Who owns synergy realization by workstream?
This is why so many integrations feel busy but incoherent. Reporting lines get announced before decision rights are designed. Governance meetings start before accountabilities are assigned. Process mapping begins before leaders decide what must be common and what can remain different.
What to do: force clarity on five design choices early.
First, define enterprise versus local decisions.
Specify which decisions must sit at group level and which remain with business units, regions, or plants.
Second, name single-point owners.
Joint ownership sounds collaborative but often produces drift. Every critical process and synergy target needs one accountable owner.
Third, set governance tiers.
Not every issue belongs in the executive committee. Define what gets resolved at operating review, functional council, integration steering committee, or CEO level.
Fourth, decide the standardization logic.
Choose where the combined company will standardize by design and where it will tolerate variation for customer, regulatory, or market reasons.
Fifth, define transition states.
The Day 1 model, the 90-day model, and the end-state model may be different. McKinsey notes that merger operating model design often requires interim states before the final design is reached.
If those five choices are unclear, the organization will create its own answers. Usually badly.
