Most mergers fail after the close, not in the model. The thesis can be sound and the synergy math can look careful, and the deal still misses because nobody owns the work that turns the promise into operating results. Ask why mergers fail project management work and the answer is the delivery system: it is weaker than the deal. Leaders who want the value they announced have to watch momentum, dependencies, decision rights, and synergy ownership in the first year, not only the closing checklist.
Talk with a MustardSeed PMO expert about a live integration
The hard part of a merger is the period after close. In a McKinsey survey of deal executives, integrating the acquired company was the stage leaders found hardest. The first 12 to 18 months after close had a significant effect on whether the merger succeeded. That window is when milestones slip and the top team discovers it is not aligned.
McKinsey's look at a decade of large deals also separates the deals that kept their promise from the ones that did not. About 72 percent of successful mergers maintained organic growth in the first year. Only about 33 percent of the deals that failed did the same. Leading deals also hit or beat at least half of their public synergy targets inside that first year. Those two facts point at a delivery problem. The merger did not fail because someone forgot a legal filing. It failed because the combined business lost its pace, and the savings or revenue in the model never became someone's job.
A 2004 McKinsey review of 160 mergers reached a related conclusion from the other direction. The average buyer overestimates the synergies a deal will yield, and a small error in that estimate is enough to wipe out the premium paid to the seller. Top-line synergy estimates were often inflated. One-time costs ran higher than planned. The time required to capture savings was longer than the model assumed. Project management is how a leadership team finds those errors while there is still time to change the plan.
None of this is a reason to treat "70 percent of mergers fail" as a planning number. That figure is repeated so often that it has stopped meaning anything specific. Use the comparisons you can act on: did organic growth hold, and did half of the named synergies show up in year one?
The same five conditions show up when an integration starts to miss. Each one is a project-management failure, and each one is visible before the quarterly numbers confirm it.
| Failure | What leaders notice | What it costs | The control that prevents it |
|---|---|---|---|
| Lost operating momentum. | Core customers, launches, or plant output slip while integration meetings multiply. | The base business that was supposed to fund the deal starts to shrink. | A short list of protected operating metrics, reviewed in the same forum as integration status. |
| The deal-to-delivery handoff. | The closing team moves on. The people running day-to-day work inherit a plan they did not test. | Assumptions about leadership, customers, and timing surface only after the clock is running. | A named integration lead in the room before close, with authority to challenge the synergy case. |
| Unowned dependencies. | Finance, IT, HR, and operations each report green while cross-team work waits. | Rework, missed Day 1 commitments, and a schedule nobody can explain. | One integrated plan with an owner for every cross-functional dependency. |
| Unclear decision rights. | Routine calls escalate, or they stall because two leaders both believe they decide. | Slow calls on pricing, people, systems, and customers. | A written decision map for the choices that move value, with one decider each. |
| Synergies with no owner. | The model names a savings or revenue figure. Six months later nobody can say where it stands. | Value that was paid for at close never reaches the P&L. | Each synergy has a baseline, an owner, a date, and a reported result. |
These are not five separate projects. Momentum fails when dependencies and decisions consume the operators who should be running the business. Synergies fail when nobody has the right to stop a workstream that is busy and still off the value case.
A typical deal splits the people who build the thesis from the people who have to deliver it. Corporate development negotiates and closes. An integration leader, often a COO or a VP of integration, receives a 100-day plan and a leadership team they have not watched under pressure. The deal team moves to the next transaction. That handoff is structural. It is not a personality problem, and calling it "culture" usually means the diagnosis stopped too early.
Pre-close interviews do not close the gap. A CEO two weeks from learning whether they still have the job will describe the leadership story that gets the deal done. They are unlikely to volunteer the conflict between two direct reports that has been managed quietly for a year. The integration team then launches on those assumptions. The cost shows up around day 30 or day 45, when straightforward decisions start escalating and the 100-day plan accumulates delays nobody can explain.
The fix is not another interview guide. Put the person who will run the integration in the challenge of the synergy case before close. Give them a short window after close to test whether the operating leaders can deliver the plan. If the answer is no, change the plan or the roles while the organization still expects change.
Workstreams go green for a reason. Each function can complete its own list. Finance opens the accounts. IT migrates a system. HR transfers employees. The failure sits in the work that needs two of those teams at once. A pricing change may need sales, finance, and a new label on a regulated product. A plant cutover may need procurement, payroll, and a customer notice on the same day.
MustardSeed saw that pattern on a global food manufacturer's post-acquisition integration, a multi-billion-dollar deal spanning four countries and more than 120 people. Legal, IT, HR, R&D, finance, tax, procurement, and commercial teams were all in motion. There was no integrated plan, no governance model, and no decision framework. Workstreams ran as silos. Priorities conflicted. Deliverables were reworked. Meetings multiplied without producing decisions. The program was behind schedule and trending toward failure until one plan, task-level ownership, and a tighter meeting rhythm replaced the parallel lists.
Decision rights fail the same way, one call at a time. If two leaders can both approve a customer exception, neither will. If every exception has to reach the steering committee, the committee becomes the bottleneck and the operators stop raising issues. A useful decision map is short. It names the few choices that move customers, cost, people, or regulatory standing, and it names one decider for each. Everything else should be settled inside the workstream.
Leaders who want a broader view of how dependencies and decision rights erode post-acquisition value creation can use that as the portfolio lens. This article stays on the single-deal failure modes.
A synergy that lives only in the investment memo is a claim, not a result. McKinsey's integration research treats early proof as part of the deal's credibility: the deals that worked had delivered at least half of their public synergy targets within a year. That standard is useful even when a company has not published a target. Pick the few synergies that justified the premium, give each one an owner, and report a baseline and a current result in the same forum that reviews the schedule.
Three estimating errors from McKinsey's 160-merger review are worth building into that report:
If a synergy cannot be tied to a baseline the owner already measures, it is not ready to be promised. That test does more to prevent a missed deal than another workshop on culture.
The first 90 days will not finish the integration. They will tell you whether the delivery system can carry it. Four signals are enough. None of them requires a new software platform.
On the food-manufacturer integration, stability returned within weeks once the plan, the ownership, and the meeting load were fixed. Rework dropped, and the team stopped using meetings as a substitute for decisions. The lesson for a leader is practical. If those four signals are red at day 45, adding more status meetings will not repair them.
Regulated businesses feel this sooner than others. A life-sciences, food, or financial-services combination often has filings, quality systems, and customer notices on the same dependency path as the cost synergy. Slipping the filing does not only slip a task. It slips the date the synergy was allowed to start. A project delivery risk management framework is the right place to record that kind of dependency. It is not a substitute for naming the owner.
Knowing why a merger's delivery fails is not the same as running the integration. A phased post-merger integration checklist still has a job: Day 1 readiness, the first 30 days, and the work after day 90. Use it once you know which failure mode you are trying to prevent. Do not let the checklist become the strategy.
This diagnosis also does not design the governance forum. A PMO governance framework answers who sits where and how issues escalate across a portfolio. An integration needs a thinner version of that idea: one plan, one decider for the choices that move value, and a cadence short enough that a missed dependency surfaces inside a week. Building the full committee structure before those three exist is how programs get busy and stay late.
It is not legal, tax, or valuation advice. Overpaying, a weak strategic fit, and a regulatory block are real ways deals fail, and they belong to the people who priced and cleared the transaction. Project management cannot repair a price that assumed synergies the organization cannot deliver. It can stop the organization from discovering that fact a year late.
Some integrations can be run by the operators who already know both businesses. Bring in outside delivery leadership when the deal itself has become the work: several countries, a regulated product, more than a handful of functions, or a closing team that has already moved on. The trigger is not headcount. It is the absence of a single owner for dependencies, risks, and decisions.
MustardSeed's M&A integration project support is built for that gap. The work ranges from the governance and master schedule a team needs before Day 1, to embedded execution across workstreams, to senior leadership of an integration management office through stabilization. The point of that support is the same test this article uses. Someone has to own the plan, the cross-team work, and the synergy number, or the merger fails in delivery even when the deal was sound.
A portfolio of deals raises the stakes. Private equity and corporate development teams that close repeatedly cannot afford to relearn the handoff on every transaction. The delivery conditions above are repeatable, which means the controls can be repeatable too.
Ask MustardSeed to review the delivery risks on a current deal. Reach the team at https://www.mustardseedpmo.com/contact-our-project-management-experts-mustardseed-pmo.
They fail because the value was assumed rather than managed. Integration is the stage executives find hardest, and the first 12 to 18 months decide whether milestones and the top team hold together. Lost operating momentum, a weak handoff from the deal team, unowned dependencies, unclear decision rights, and synergies with no owner are the delivery conditions behind most of those misses.
Culture is often the label used when the diagnosis is incomplete. Clashes are real, but the failures leaders can prevent show up as specific delivery gaps: decisions that escalate, work that sits between two functions, and a synergy nobody can measure. Fix those and many "culture" complaints shrink, because people can see who decides and what is owed.
Often by day 30 to day 45. Watch whether base-business metrics are holding and whether the open decision list is shrinking. Check that every cross-team dependency has an owner, and that each promised synergy has a baseline and a current result. A green status report that cannot answer those four questions is not evidence of control.
A checklist prevents missed tasks. It does not prevent a bad handoff or an unowned synergy. Use a checklist for Day 1 and the first 90 days, and use a separate review for momentum, decision rights, dependencies, and value. Completing the list while the base business slows is still a failed integration.
Bring it in when no single owner is tracking dependencies, risks, and decisions, especially on multi-country, regulated, or multi-function deals. Outside leadership is also warranted when the people who built the deal thesis have already moved on and the operators inherited a plan they did not test.
