Why operational excellence either proves itself or exposes itself in M&A
The deal closes.
Months of due diligence. Weeks of negotiation. Legal complexity that consumed armies of advisers. A price agreed. A board signed off. An announcement made.
And then the real work begins.
The work that the financial model didn’t fully capture. The work that the integration plan described at a level of abstraction that made it look manageable. The work that is, in practice, the most complex operational challenge most leadership teams will ever face.
Acquisition integration.
Every manufacturing business that grows through M&A eventually confronts a specific truth: the value that was identified in due diligence — the synergies, the capabilities, the market access, the cost reduction opportunity — does not extract itself. It has to be released, deliberately, by people who understand both the strategic intent and the operational reality of what they are integrating.
Most businesses have financial integration processes. Legal integration processes. HR integration processes. Brand and communications integration processes.
Very few have an operational integration methodology.
This post is about what one looks like — and why its absence is one of the most common reasons that M&A deals deliver less than their strategic promise.
1. What Due Diligence Misses
Due diligence is thorough in the dimensions it examines.
Financial performance. Legal risk. Commercial pipeline. Customer concentration. Market position. Technical capability. Key people.
It is systematically thin in one dimension: operational system quality.
The due diligence team can assess whether the acquired business has a quality management system. It cannot reliably assess whether that system is genuinely embedded in daily operations or exists primarily on paper. It can review the OEE figures. It cannot assess whether those figures are calculated consistently with the acquirer’s methodology or whether they represent a definition that would produce a very different number if recalculated. It can review the headcount structure. It cannot assess the actual capability of the people within it, or the degree to which critical knowledge is concentrated in individuals rather than embedded in process.
The result is a deal model that captures the headline operational performance of the acquired business but not the quality of the operating system that produces it. And when integration begins, that operating system is the first thing that matters.
Because integration is not the joining of two financial statements. It is the joining of two operating systems — two sets of processes, standards, management behaviours, measurement conventions, and cultural norms that have been built independently, often over decades, and that are now being asked to coexist or combine.
How that joining happens determines whether the deal value is realised or whether it is absorbed by integration friction.
2. The Integration Failure Modes
There are three ways operational integration typically fails.
Imposition. The acquirer assumes that its operating model is superior and applies it to the acquired business rapidly and comprehensively. The acquired business’s processes are replaced with the acquirer’s. The acquired business’s management systems are migrated to the acquirer’s platforms. The acquired business’s improvement methodology is superseded by the acquirer’s programme.
This is the fastest approach. It is also the most destructive.
It destroys value in three ways. It disrupts the operational stability of the acquired business during the transition — performance dips, sometimes significantly, while the new systems and processes are embedded. It drives away the people who built the acquired capability and who are not willing to simply implement someone else’s system. And it discards whatever was genuinely good about the acquired business’s operating model — the things that made it worth acquiring in the first place.
Hands-off. The acquirer leaves the acquired business to operate independently. Integration is financial and commercial — shared reporting, combined sales efforts, unified customer interface — but operational integration is deferred or avoided entirely. The acquired business continues to run its own way.
This is the most comfortable approach. It is also the most expensive.
It leaves synergies unrealised. It allows two different operating cultures to calcify rather than converge. It creates a permanent outlier in the operating portfolio — a business that shares a name but not an operating model, that cannot benefit from the group’s knowledge or capability, and that cannot contribute its own.
And it defers the difficult work rather than avoiding it. The integration that doesn’t happen in year one has to happen eventually. By year three or year five, it is harder — the divergence is deeper, the resistance is greater, the people who could have bridged the two cultures have moved on.
Bilateral exchange. The acquirer and the acquired business approach integration as a genuine exchange. The acquirer brings a defined operating model — the non-negotiables that apply across the group. The acquired business brings its own operational intelligence — the things it does well that the acquirer can learn from. The integration is a process of mutual assessment, deliberate alignment, and calibrated exchange.
This is the right approach. It is also the most demanding. It requires the acquirer to have a defined operating model worth bringing. It requires the intellectual honesty to look at the acquired business as a source of capability, not just a recipient of it. And it requires the operational skill to assess both sides of the comparison with genuine rigour.
3. The Operational Due Diligence the Deal Team Didn’t Do
The first step in good operational integration is the operational assessment that should have happened in due diligence but didn’t — or didn’t go deep enough.
This assessment is not about validating the financial model. It is about understanding the operating system of the acquired business in enough detail to make informed integration decisions.
It covers six dimensions.
Management system maturity. How does the business manage its own performance? What is the quality of the daily management process? What is the relationship between the data that is reported and the reality it is supposed to represent? Is improvement activity genuinely embedded or is it periodic and event-driven?
Process capability and stability. What is the actual capability of the key production and support processes? Not the headline OEE or the summary quality metrics — the underlying process capability, assessed at a level that reveals whether the headline numbers are reliable and what they are hiding.
Knowledge architecture. Where does the critical operational knowledge live? In documented processes, in systems, or in people? If in people — which people, how many of them, and what is the retention risk? The knowledge architecture of the acquired business is its most fragile operational asset during integration, and it is almost never assessed in the deal process.
Leadership capability. What is the genuine capability of the management team at each level? Not their tenure and their titles — their ability to lead through change, to operate within a new management framework, to develop their own people. Integration stress-tests leadership more severely than normal operations. Knowing which leaders will thrive and which will struggle is critical information for integration planning.
Cultural norms. What are the informal rules of the acquired business — the things that are true about how it operates regardless of what any policy or process document says? These norms are not visible in due diligence data. They emerge from conversations with people at multiple levels, from observation of how meetings are run and decisions are made, from listening for what is said and what is not said.
Operational strength and weakness. What does this business do genuinely well — at a level that the acquirer could learn from? And where are the gaps that the acquirer’s operating model would close?
This assessment requires operational expertise — not financial or legal expertise. It requires people who can walk a factory floor, hold a conversation with a production manager, read a process capability chart, and form a judgement about the quality of what they are seeing.
Most deal teams don’t have those people. That is a structural gap in how acquisitions are prepared.
4. The Integration Sequencing Question
One of the most consequential decisions in operational integration is sequencing — what to integrate first, what to leave until later, and why.
Most integration plans sequence based on visibility and commercial urgency. The customer-facing elements are integrated first — the commercial team, the brand, the customer interface. The operational elements are integrated in a second wave. The systems and processes come last, often years after the deal closed.
That sequencing reflects commercial priorities. It does not reflect operational risk.
The operational integration that happens last is the integration that shapes whether the deal value is realised. And the decision to sequence it last means that the most complex, most disruptive, and most capability-dependent work happens when the integration energy has dissipated, when the people who understood the original operating model have moved on, and when the political will to make difficult changes has been consumed by the commercial integration.
Better sequencing starts with the operating system.
Stabilise first. In the immediate post-deal period, the priority is operational stability — maintaining the performance of both businesses while the integration is being designed. Changes that are not necessary for stability should not be made yet. The business that was acquired was worth acquiring partly because it was operating. Destabilising it in the first ninety days is a value destruction choice.
Assess before integrating. Before deciding what to change, understand what exists. The operational assessment described in the previous section is not a day-one activity — it is the activity that determines what day-one and day-thirty and day-ninety should look like.
Integrate the management system before the processes. The management cadences, the review structure, the escalation logic — these are the infrastructure of operational integration. Aligning them early creates the conditions for process integration to happen coherently, with the right people having the right conversations at the right frequency. Trying to integrate processes without first aligning the management system is trying to build on an unstable foundation.
5. What the Acquired Business Knows
The most consistent mistake in acquisition integration is the assumption that value flows in one direction.
The acquirer brings the scale, the capital, the market access, the operational system. The acquired business receives these things and benefits from them.
In practice, the acquired business almost always has things the acquirer needs.
Technical knowledge that the acquirer’s engineering teams don’t have. Customer relationships built over decades that the acquirer’s commercial team can access but cannot replicate. Process innovations that the acquirer’s improvement programme hasn’t developed. A management culture — more agile, more direct, more entrepreneurial — that is partly what made the business attractive in the first place and is at risk of being eliminated in the integration.
The integration that fails to identify and deliberately preserve these things is destroying value it paid to acquire.
The integration team needs to operate with genuine curiosity about what the acquired business knows — not just what it has. And the acquirer’s leadership team needs to be genuinely open to the possibility that some of what it finds will require the acquirer to change, not just the acquired business.
That posture is rare. It is also one of the most reliable indicators of integration success.
6. The Knowledge Retention Problem
In the months following a deal close, the acquired business loses people.
Some leave because of uncertainty. Some leave because the cultural change is not what they signed up for. Some leave because the acquirer’s talent process identifies them as redundant to the combined structure. Some leave because better opportunities emerge when the market learns they are available.
Every person who leaves takes knowledge with them.
In the early post-deal period, when the operational knowledge of the acquired business has not yet been documented, assessed, or transferred — when it still lives primarily in the heads of the people who built it — the people risk is the operational risk.
A retention strategy for the acquired business’s critical knowledge carriers is not an HR nice-to-have. It is an operational imperative. Identifying who holds the knowledge that is most critical to integration success, understanding their motivations, and designing specific retention approaches — in terms of role, recognition, and development — is knowledge management in the most literal sense.
And where retention is not achievable, knowledge transfer — structured, systematic, urgent — is the alternative. Before the people who know leave, extract what they know into documented process, into trained colleagues, into the institutional record of the combined business.
Most integration plans treat this as self-evident and therefore don’t design for it explicitly. The result is that knowledge walks out the door in the first six months, and the integration proceeds on the basis of an operating system that is no longer fully understood by the people who are supposed to be running it.
7. Measuring Integration Success
The measures by which most integrations are assessed are financial — synergy delivery against the deal model, cost reduction against the integration budget, revenue growth against the combined commercial plan.
These are lagging indicators. They measure the output of the integration, not the quality of the process that produces the output.
The operational integration metrics that matter — the ones that predict long-term value realisation rather than just reflecting short-term performance — are different.
Operational stability during transition. Is the acquired business maintaining its pre-deal performance levels during integration? Or is the integration activity itself disrupting the business it is trying to improve?
Knowledge retention rate. Are the critical knowledge carriers still in the business twelve months after close? Are the capabilities that made the acquisition attractive still present in the combined business?
Management system convergence. Are the two operating systems genuinely integrating — common management cadences, common improvement methodology, common language — or are they coexisting as parallel cultures with a unified financial report?
Cross-business knowledge transfer. Is the knowledge that was identified as best practice in the acquired business being actively transferred to the acquirer’s operations? Is the learning genuinely bilateral?
These metrics are harder to define and harder to measure than synergy delivery. They are also better predictors of whether the deal delivers its strategic promise or simply its financial model.
Final Thought
Acquisition is a strategy. Integration is the execution.
The gap between what was promised in the deal model and what is delivered in practice is almost always an integration gap — a failure of the execution to match the strategic intent.
That gap has multiple causes. Unrealistic synergy assumptions. Poor retention of acquired capability. Cultural incompatibility that wasn’t assessed in due diligence. Commercial market changes that altered the strategic rationale.
But the most preventable cause — the one that careful operational integration methodology most directly addresses — is the failure to understand, preserve, and combine the operating systems of the two businesses in a way that releases the value both sides bring.
The playbook for that work is not complicated. Assess before integrating. Stabilise before transforming. Exchange before imposing. Retain the knowledge before it walks. Measure the integration quality, not just the financial output.
What is complicated is the discipline to follow the playbook when commercial urgency, internal politics, and executive impatience are all pulling toward faster, simpler, more visible action.
The businesses that realise the full strategic value of their acquisitions have made the decision that operational integration excellence is not an optional refinement. It is the mechanism by which the deal value is released.
Without it, the model stays a model.
Three questions.
In your most recent acquisition, when was the operational assessment conducted — before the deal closed or after, and how deep did it go?
What knowledge has left the acquired business in the past twelve months that was not formally identified, captured, or transferred before it went?
And if you mapped the operating systems of the two businesses today — the management cadences, the improvement methodology, the measurement conventions, the leadership standards — how close are they to genuinely integrated, and what is the remaining gap costing?
adam
Leave a Reply