Reference studies, notably in Harvard Business Review, have pointed for decades at a stubborn finding. Indeed, 70 to 90% of mergers and acquisitions fail to deliver the expected value. The paradox is that the cause rarely lies in the deal itself. The target was sound, the price defensible, the investment thesis solid. What fails is the post-merger integration. Here are the four most frequent value-destruction mechanisms in a post-merger integration, and their antidotes.
1. Synergies stay in the business case
Teams quantify synergies carefully to convince the board. Yet they rarely manage them as a program after closing. Indeed, no single owner, no milestones and no measurement follow. Two years later, both IT landscapes still coexist and duplicate contracts keep running. The antidote is simple: treat every synergy as a deliverable. Each one then gets a value, a deadline and a named owner. You track them at the same cadence as the rest of the program.
2. Talent attrition
Prolonged uncertainty drives away precisely the people you paid for. Think of the experts, the key sales people, the managers who hold teams together. The antidote comes down to two words: pace and communication. Indeed, a milestone-driven integration shortens the period of doubt, if you announce it and keep it. As a result, it reduces the attrition.
3. Decision paralysis
Who decides, on what scope, under what rules? Until you install integration governance, every trade-off escalates, stalls or happens twice. The antidote is an operational integration governance within the first weeks. It rests on a clear mandate, notably on the integration model you choose workstream by workstream: full integration, partial alignment or preserved autonomy.
4. IT as the blind spot
Connecting two IT landscapes often passes for a technical matter to delegate. In fact, it is the critical path of most synergies. Indeed, without IT convergence, there is no contract consolidation, no process harmonization, no unified view of the customer. Moreover, connecting without auditing the acquired entity’s security amounts to importing its vulnerabilities. The antidote: make IT a first-rank workstream of the post-merger integration, with its cyber component.
Post-merger integration: the takeaway
An acquisition does not create its value at signature. That value appears, or disappears, in the eighteen months that follow. Thus, the difference comes down to one thing: a post-merger integration that you govern as a program, not manage as a pile of projects.