Building the Integration Mechanics

Decision Ownership, Information Flow and Issue Resolution

In this third installment of our Five Principles That Make or Break Merger Integration series, we turn to two final principles, Cross-Functional Accountability and Transparency and Escalation Discipline.

The first installment of our series introduced five principles that emerged from our engagement on a recent $12 billion consumer merger and served as practical guardrails for large-scale integration: Customer Service First, Stability Over Speed, Test Before You Transform, Cross-Functional Accountability, and Transparency and Escalation Discipline. The second installment discussed how to limit impact to customers in practice across three domains in which integration risk most directly reaches them.

For Cross-Functional Accountability and Transparency and Escalation Discipline, we examine each through the three operational domains in which these principles are most consequential in practice: Technology and Data Integration, End-to-end Operations and Customer Support. In each domain, the pattern is the same: weak accountability and transparency create the problems, and weak escalation discipline delays the response.

Establishing Cross-Functional Accountability

In a large merger, accountability gaps rarely stem from disengaged leaders. More often they stem from ambiguity in ownership, effectively stalling momentum and creating space for operational failures without a clear path to resolution. Leadership merely defined at a functional level does not adequately support a cross-functional post-merger operating model.

Technology and Data Integration. Data migration and system connectivity require cross-functional ownership to align the technical execution to the business logic it must serve. Without a centralized integration body to coordinate across functions, ownership gaps will surface. Defining accountability, not before go-live, but rather before integration planning even begins, creates a strong foundation to plan and execute complex mergers.

End-to-end Operations. Planning and production span commercial, manufacturing and supply chain functions, and in a large merger, each legacy company brings its own processes, systems and operational logic. Misalignment across these functions does not stay contained; variation at one handoff compounds downstream, degrading order fill rates, inventory positions and service levels across the network. Achieving high process capability requires a centralized owner to align supply chain logic, execution standards and demand forecasting across the combined entity before operational gaps become structural ones.

Customer Support. Customer support as a function cannot absorb accountability for integration outcomes it does not own. The function needs a formal, designed connection to the operational workstreams generating customer impact through various customer-facing key performance indicators (KPIs) such as call volume and order volume. Customer-facing KPIs provide insight into the successes and failures of internal operations during and post-merger. Building a closed loop between customer-reported failures and internal issues from the start reduces resolution time and prevents the customer support function from becoming inundated with upstream failures.

Transparency and Escalation Discipline

Even with strong governance, issues can manifest undetected. Integration failures are often caused by information that surfaces too late or goes to stakeholders who lack decision rights. The principle of Transparency and Escalation Discipline governs how information moves and how issues reach leadership before a contained problem becomes a crisis.

Technology and Data Integration. Escalation pathways for system disruptions should be designed alongside the cutover plan, with triggers tied to migration completeness and validation thresholds. Triggers should be determined proactively, before service failures begin to surface. A KPI framework allows for insight into the successes and failures of system integration. These indicators signal system misses early, before downstream impacts are exacerbated. Defining those thresholds in advance transforms escalation from a judgment call made under pressure into an outlined protocol.

End-to-end Operations. Interim tracking solutions preserve leadership’s ability to respond before availability constraints reach customers. Planning and production performance should be measured against defined service outcome metrics, such as in-stock rate, order fill and on-time availability, rather than against functional measures alone. Each function should carry escalation triggers tied to those outcomes, so that structural misalignment surfaces upstream and reaches leadership while it can still be corrected, not after it has already shown up at the shelf or in the customer’s order. When an organization’s integration plan solely accounts for functional measures without carrying escalation triggers, structural problems stay invisible until they reach the customer as a stockout or missed order, by which point leadership has lost the early window to respond.

Customer Support. Call volume is a lagging indicator demonstrating the successes and failures of integration. Categorizing customer impact and tying these buckets to internal failure modes in near real-time allows businesses to address the root cause of common complaints. Building that categorization into the support model from the start, alongside a defined escalation path to the right operational owners, allows leadership to intervene before volume reaches a level that overwhelms capacity. Aligning internal and external messaging when disruptions occur signals organizational control and builds confidence with employees, customers and investors during a time when that confidence is both fragile and essential.

Bringing the Series Together

Across the three installments of our series, the five highlighted principles resolve into a single discipline: keep the customer whole while rebuilding the company that serves them. Part 1 outlined the five principles. Part 2 showed how to protect the customer in the moments during which integration risk reaches them most directly. Part 3 turned internal, looking at who owns each decision and how quickly a problem travels to someone who can act on it.

These last two are the principles most often underestimated, with integration focused on building a strategy rather than how to execute. Integrations fail on ambiguity about who owns what, and on information that reaches leadership too late to act. Clear ownership and disciplined escalation are what turn a sound plan into an organization that operates as one company.