Why 70% of M&A Integrations Fail and What the Data Actually Shows
When we run network analyses on merged organizations one, two, sometimes three years after close, the pattern is consistent. The org chart says one company. The network data says two. Sub-networks are still primarily working with their legacy colleagues. Distinct subcultures are operating side by side inside the same unit, holding different beliefs about what good looks like, what success means, what the work is actually for. The legal entity merged. The organization did not.
That gap, between structure on paper and the structure that drives behavior, is where most integrations quietly fail.
The Org Chart Gets Merged. The Organization Doesn't.
There's a reason integration teams pour enormous effort into the structural combination: it's the part that can be planned. Headcount decisions, reporting lines, system consolidation, real estate. These are problems with defined endpoints.
The informal structure has no defined endpoint. It's the accumulated result of years of working relationships, trust built through repeated interaction, and shared shorthand about how things get done. Trust is slow. Integrations are fast.
Organizations put enormous resources into planning the structural combination and almost none into the informal structures that will determine whether the plan actually works. That's not a failure of intent. It's a failure of visibility: most integration teams have no way to see the informal org at all.
Three Mistakes That Compound the Problem
Mistake 1: Mistaking structural integration for cultural integration.
The more precise version of this problem isn't culture clash. It's that teams are operating with different definitions of what good looks like. Different frames for success. And those frames don't change just because the org chart does.
In a study of a major merger, Rob Cross found that the unit with the slowest revenue growth had a significantly lower proportion of cross-legacy ties. The unit that underperformed had already been formally restructured. Employees had been blended on paper. But the informal networks hadn't moved. And when researchers went deeper, the reason wasn't resistance. It was that people were optimizing for fundamentally different things. In meetings, both sides felt they were talking past each other, because they were: they cared about different outcomes, and neither side knew it.
The unit that performed best had a much higher proportion of ties connecting employees across legacy organizations. That was a measurable structural property of the network, and it showed up in the revenue line.
Mistake 2: Stakeholder mapping stops at the top.
Most integration PMOs identify the senior opinion leaders: the most visible, most central people in the organization. These are the people who appear on integration plans, who are briefed first, whose buy-in gets tracked.
What we've consistently found in our work is that the people who actually shape how rank-and-file employees interpret change aren't always the ones on the integration plan. They're informal influencers sitting two or three levels deeper in the network: the person everyone goes to before they make a decision, the one whose read on a situation gets quietly circulated before any town hall lands. They carry the legacy assumptions that either get bridged or don't. And they're almost never in the room when integration strategy gets set.
Senior alignment without that layer produces compliance at the surface and skepticism underneath.
Mistake 3: Silos don't dissolve. They calcify.
In any mature organization, silos are a known problem. Information moves through established channels. People communicate through existing relationships. Breaking down silos is difficult under normal conditions. In a merger, the problem compounds.
You now have two sets of pre-existing silos from two organizations. Without deliberate intervention, those silos don't dissolve. They calcify. The new organization inherits both structures and often adds a third layer of friction at the seam where they meet. When communication channels are almost entirely legacy-to-legacy, you get two organizations living inside one legal entity.
What High-Performing Integration Teams Do Differently
Here's what we keep seeing in the data.
Cross-legacy tie density is a leading indicator, not a lagging one. The best-performing units in Cross's research had measurably higher cross-legacy connections. This is trackable before integration stalls. Teams that monitor network formation in the first six to eighteen months can intervene before patterns lock in, rather than diagnosing the problem years later.
Informal influencers do more belief-shifting than senior leaders. Two or three levels below the leadership cohort, there are people whose informal authority shapes how everyone else interprets what's happening. Engaging them early, not just informing them but genuinely working with them on the integration narrative, is what moves the underlying belief structure. Senior alignment without that layer produces compliance at the surface and skepticism underneath.
Shared goal-setting accelerates alignment faster than shared org structure. Research on goal alignment finds that working across legacy groups toward explicit 90-day shared objectives can reduce attrition significantly and improve profitability within six to twelve months. When employees can draw a line from their work to shared objectives, legacy identity becomes less central. The structural integration creates the conditions. The goal-setting does the actual work.
Deliberate bridging is what moves the informal network. Reorganizing reporting lines does not break down silos. Cross-silo leadership requires specific investment: structured cross-legacy working groups, joint projects with shared accountability, situations where the only path to success runs through the other side. These create the conditions for new ties to form. Left to default behavior, people communicate through established channels, and established channels are legacy channels.
The Part That Doesn't Go on the Plan
It's easy to plan around the structured stuff. It's hard to plan around the stuff that makes the structured stuff work.
The informal organization is not a soft problem. It is the implementation layer that the entire integration plan depends on. And in most deals, it goes unexamined until the results make the gap impossible to ignore.
About the Author
Victor Bilgen is the Founder of BridgeLayer Analytics. He spent 13 years at the McChrystal Group running diagnostics and network analysis for Fortune 1000 executives, and built BridgeLayer because the gap between organizational insight and organizational action kept showing up in the same place: the work that comes before the recommendations. He is a contributing author to The Social Capital Imperative (Oxford University Press, 2025).
