Mergers and acquisitions are announced with optimism. Synergies are projected, value creation is modelled, and integration timelines are set. Then the work begins — and the gap between the deal thesis and operational reality becomes apparent. Research consistently shows that more than half of all mergers fail to deliver the value they promised. The most common reason is not a flawed deal. It is a failed integration.
The first 100 days after close are disproportionately important. Decisions made — or deferred — in this window shape the integration trajectory for years. Talent is retained or lost. Systems are rationalised or duplicated. Cultures are bridged or fractured. The organisations that navigate this period well do so not by accident, but by design.
Why integration fails before it starts
The most damaging integration mistakes are made before day one. Integration planning that begins at close — rather than during due diligence — consistently underestimates the complexity of what has been acquired and overestimates the speed at which two organisations can be combined.
Effective integration planning starts during due diligence with a clear-eyed assessment of the target's operating model, technology landscape, data architecture, regulatory obligations and cultural norms. The integration thesis — what will be combined, what will remain separate, and in what sequence — should be substantially formed before the deal closes. Organisations that treat integration planning as a post-close activity routinely find themselves making consequential decisions under time pressure, with incomplete information.
The four integration workstreams that determine outcomes
Across complex integrations, four workstreams consistently determine whether the combined entity creates or destroys value. Each requires dedicated leadership, clear accountability and a realistic timeline.
Operating model and organisational design
The most consequential early decision is the target operating model for the combined entity. Organisations that defer this decision — maintaining parallel structures while "integration proceeds" — create ambiguity that drives talent attrition and slows every other workstream. The operating model does not need to be fully implemented in 100 days, but it needs to be decided. People need to know where they stand.
Technology and data rationalisation
Most integrations inherit two of everything: two ERP systems, two data platforms, two identity directories, two sets of security controls. The rationalisation roadmap — which systems survive, which are decommissioned, and in what order — is one of the most technically complex and politically charged decisions in any integration. It requires both technical depth and organisational authority. Deferring it creates compounding technical debt that becomes progressively harder to unwind.
Regulatory and compliance alignment
Regulated industries — financial services, healthcare, government, utilities — face integration complexity that goes beyond operational rationalisation. Licences, accreditations, data sovereignty obligations, privacy frameworks and sector-specific compliance requirements must be mapped across both entities from day one. Compliance gaps discovered late in an integration are expensive to remediate and can expose the combined entity to material regulatory risk.
Culture and talent retention
The talent risk in any integration is front-loaded. Key people — those with institutional knowledge, client relationships and delivery capability — make their decision to stay or leave in the first weeks after close. Organisations that communicate clearly, move quickly on role decisions and demonstrate respect for the acquired entity's culture retain the talent they paid for. Those that leave people in uncertainty for months consistently find that the best people leave first.
Governance for speed and accountability
Integration governance is different from business-as-usual governance. The decision velocity required in the first 100 days is incompatible with standard committee structures and approval cycles. Effective integration governance has three characteristics.
Key insight
"Integration governance must be designed for the speed the program requires — not adapted from the governance structures the organisation already has."
A single integration leader with real authority. The integration management office must be led by someone with the mandate to make decisions across both legacy organisations — not a coordinator who escalates everything. This person needs direct access to the CEO and the board, and the authority to resolve conflicts between workstream leads without referral upward.
Daily operating rhythm in the first 30 days. The first month of integration requires a cadence that most organisations are not accustomed to. Daily stand-ups across workstream leads, weekly executive reviews, and a clear escalation path for decisions that cannot wait. This intensity is not sustainable indefinitely, but it is essential while the integration is most fragile.
A live integration risk register. Integration risk is dynamic. Issues that are minor in week one can become critical by week four if they are not addressed. A live risk register — reviewed at every executive session — ensures that emerging issues are visible before they become crises. The register should be owned by the integration leader, not delegated to a program management function.
The capability gap most organisations underestimate
Post-merger integration is a specialist discipline. It requires practitioners who have navigated the specific challenges of combining two operating entities — not generalist program managers who are encountering these challenges for the first time.
The most common capability gap we observe is in the intersection of technology rationalisation and regulatory compliance. Organisations that can manage the operational integration competently often lack the depth to navigate the data governance, privacy and security implications of combining two technology estates — particularly in regulated industries where the compliance obligations are material and the consequences of getting it wrong are significant.
Bringing in specialist capability for the integration period — rather than stretching internal teams beyond their experience — is consistently the more cost-effective approach. The cost of a failed or delayed integration dwarfs the cost of the right capability in the room.