Top 3 Reasons Synergy Assumptions Fail, and How Behavioral Data Fixes Them

Short answer

Synergy assumptions rarely fail because the math was wrong. They fail because the math assumed something about human behavior that was never tested. Three failure patterns account for most of the gap between projected and realized synergies, and all three are visible in behavioral data before the deal closes, not after the shortfall shows up in a quarterly review.

1. The synergy assumes coordination that was never going to happen

Every cross-functional synergy is a coordination bet dressed up as a number. A revenue synergy from cross-selling assumes two commercial teams will share leads, trust each other's judgment, and prioritize the combined pipeline over their own. A cost synergy from consolidating operations assumes two functions will align on process without a turf fight.

The deal model treats this coordination as a given, because it has to go somewhere and the spreadsheet does not have a column for whether two department heads actually like working together. In practice, the coordination either exists or it does not, and diligence rarely checks.

The failure shows up gradually. Meetings between the two leads get shorter and less frequent. Decisions that should involve both people start routing through subordinates instead. Nobody flags it as a problem because operations look normal from the outside. Then the synergy misses its milestone and the postmortem calls it an execution issue, as if execution were a separate category from the relationship that was supposed to drive it.

What behavioral data catches. A pre-close assessment of the specific leaders responsible for a coordination-dependent synergy shows whether their decision-making styles, communication patterns, and collaboration profiles are actually compatible, not whether they were polite to each other in a management meeting. Post-close, the same signal, communication frequency, response latency, whether decisions stay joint or start fragmenting, is trackable continuously. A synergy that depends on two people coordinating well can be watched in near real time, and a coordination breakdown is visible weeks before it becomes a missed number.

2. The synergy assumes the organization can absorb the pace of change

Deal models set synergy timelines based on what looks achievable on paper: systems can be merged in six months, headcount can be rationalized in a quarter, processes can be standardized by the end of year one. These timelines are almost always built from the acquirer's own change capacity, not the target's.

An organization that has operated with high autonomy and informal decision-making for a decade does not absorb centralized governance at the same speed as one that has run on structured process the whole time. Push the first organization through a change pace designed for the second, and the synergy does not fail outright. It slows, quietly, as people find ways to preserve the working patterns they are used to underneath a compliance layer that looks correct from the outside.

This is the failure mode that gets misdiagnosed most often, because it looks like resistance or slow execution rather than what it actually is: a mismatch between the pace the model assumed and the pace the organization's behavioral profile can actually sustain.

What behavioral data catches. Resilience, adaptability, and process orientation are measurable before close. An organization with low tolerance for rapid governance change is not a reason to abandon the synergy. It is a reason to build a realistic timeline around it, sequencing the change to start where the behavioral evidence shows the least resistance and building momentum before pushing into the harder cohorts. Timelines built on behavioral evidence miss less often than timelines built on operational optimism.

3. The synergy assumes the people delivering it will still be there

A synergy owned by a specific person is a synergy that depends on that person staying engaged and staying in the role through the timeline the model assumes. Deal models rarely price this explicitly. Retention gets treated as a general HR concern rather than a line-item risk attached to specific, named synergies.

Between 47% and 75% of key employees leave within three years of an acquisition, and the departures are not evenly distributed. They concentrate in the roles where the gap between what the person expected from their organization and what the new governance model actually delivers is widest. When the person who leaves is the one who owned a synergy, the synergy does not just slow. It frequently resets, because the institutional knowledge and the relationships that made the number achievable left with them.

What behavioral data catches. Retention risk is measurable at the individual and role level before close, weighted against how critical each role is to a specific synergy assumption. This turns a generic attrition concern into a specific, addressable risk: which roles carry the highest exit probability under the exact governance changes this deal will introduce, and which of those roles sit directly underneath a synergy the model depends on. Retention structures built around this evidence protect the specific people the thesis needs, rather than applying a blanket bonus to anyone with a senior title.

Why all three patterns share the same root cause

Coordination breakdown, change-pace mismatch, and unaddressed retention risk look like three separate problems. They are the same problem measured at three different points: the deal model treats behavior as a constant when it is actually the variable everything else depends on.

Financial diligence tests whether the numbers in the model are real. Legal diligence tests whether the protections around the deal are sound. Neither tests whether the people responsible for delivering the model can actually do what the model assumes. That gap is where these three failure patterns live, and it is closeable before close, not discovered after it.