The Deal Closed. The Teams Did Not Merge.
A CEO called me ninety days after her acquisition closed. The integration plan was excellent — 400 line items, named owners, a color-coded dashboard, a program office running it. On paper, the two companies were one company.
She asked eleven of her leaders, one at a time, what the combined strategy was. She got four different answers.
Not four wordings of the same answer. Four strategies. The acquiring side described a scale play — same business, more of it. Two of the acquired leaders described a capability play — the whole point was the technology they brought. One described a market-entry play. Her CFO described a cost play, which is the version the model had been built on.
Every one of them could recite the strategy deck. None of them meant the same thing by it.
That is post-merger integration alignment, and it is not on the plan. The plan tracks systems, entities, headcount, and day-one readiness. It does not track whether the leaders running it hold the same picture of what they are building.
Only About 5% of Employees Understand the Strategy
This is not a merger problem first. It is a strategy problem that a merger makes twice as bad.
The long-standing finding is that only about 5% of employees understand their company's strategy well enough to act on it. Ninety-five percent are working hard on something, and it is not reliably the thing the strategy asked for.
Now put two companies together. You do not average the two numbers. You compound them.
Each company arrives carrying its own unstated version of what matters — how decisions get made, what "urgent" means, who has to be in the room, which numbers are real. Nobody wrote those down. They were never in a deck, so they were never in the diligence. They live in the muscle of each leadership team, and both sides assume theirs is simply how business works.
Then a combined strategy lands on top of both. Each team reads it through its own unstated version. And because the words are the same, everyone believes they agree. The disagreement stays invisible until it shows up as a stalled decision, a duplicated project, or a good leader from the acquired side quietly taking a call from a recruiter.
The failure rate on mergers has hovered between 70 and 90% for decades. The diligence keeps getting better. The models keep getting sharper. The number does not move. It does not move because the thing that breaks is not in the model.
The Integration Plan Is Not the Alignment Layer
Here is the distinction worth being precise about, because it is where most integration budgets get spent in the wrong place.
An integration plan answers *what happens and when*. Migrate the ERP by Q3. Consolidate the two sales regions. Harmonize the comp bands. It is a sequencing instrument, and a good one is genuinely valuable.
Alignment answers *what we are actually building and why*. It is not a document. It lives in whether two leaders from formerly different companies, facing a decision the plan never anticipated, choose the same way.
The plan covers the decisions you predicted. Integration is mostly the decisions you did not. And in that gap, each leader falls back on the version of the strategy in their own head — which is exactly the thing that was never merged.
This is the same failure that makes strategy die in the middle in a single company, running at double strength. Two cascades, two sets of assumptions, one deck. Sending a better deck does not fix it, which is the point a strategy communication plan keeps proving: communication volume is not understanding.
And it is not the same problem as cross-functional alignment, though it looks like it from the outside. Functional silos are one company's leaders optimizing for their own area. Post-merger misalignment is two companies' leaders holding two whole worldviews, each internally coherent, each invisible to the other. Redrawing the org chart moves both worldviews into the same boxes and changes nothing about either — which is why breaking down silos is necessary here and nowhere near sufficient.
Name the Baggage Both Sides Brought
At Lead the Endurance we call it Baggage — what a team carries into every meeting that never gets said out loud. Past failures. Assumptions. Old grudges.
In a merger, Baggage is heavier than usual and it arrives in two matched sets.
The acquired team carries "we were bought because we were good, and now we are being run by people who do not understand what made us good." The acquiring team carries "we paid a premium and they are slow to get on board." Both are sincere. Neither is said. And both run every integration meeting from the back of the room.
Watch for the tell. In post-merger meetings people say "you" and "us" long after the legal entities merged. Eighteen months in, leaders still refer to "legacy" this and "the old" that. That vocabulary is Baggage speaking, and it is a live reading of how far the alignment work still has to go.
Named out loud, Baggage loses most of its charge. A team can restructure around a thing it has said. It cannot restructure around a thing it is pretending is not there. That is why the first serious alignment session after a close is spent surfacing what each side brought — before anyone touches the combined operating model.
What Actually Makes Two Teams One Team
Two leadership teams become one team by getting through something hard together. Not by a town hall, a values workshop, or a shared drive.
That is the design behind Lead the Endurance. Leaders become Senior Advisors to Ernest Shackleton on his 1914 Antarctic expedition. The Endurance is trapped in the ice. The plan stops working. Supplies run short, the ship is lost, and the crew has to be brought home across ice and open ocean. Participants face Shackleton's real decisions, and no single leader holds all the information or all the authority.
For a merged leadership team this does something no offsite agenda does. It strips the labels. In that room nobody is from the acquiring side or the acquired side, because the situation does not care where anyone worked eighteen months ago. It cares whether the group can decide together while the ice closes.
Two things surface fast. First, the two teams' unstated decision rules become visible — one side moves on incomplete information, the other waits for the data, and now both can see it, name it, and choose which rule the combined company will use. Second, leaders stop defending their side's version and start building one version, because the expedition will not survive four of them.
We use the Big Picture Model to connect each leader's function to the combined strategy, and POW, the Power of Why, so the team builds the why themselves. A team that builds the why owns it. A team that receives the why on a slide forgets it by Friday — and a merged team forgets it faster, because it already has a why of its own that it liked better.
How to Run the First 100 Days Differently
Ask the eleven-leader question in week one. Individually, in writing, no prep: what is the combined strategy and what does it ask you to do differently on Monday? The spread in those answers is your real integration risk, quantified, before it costs you anything.
Surface both sets of Baggage before the operating model. Each side names what it carried in. Do this before the combined structure work, not after — the structure decisions get made through the Baggage otherwise.
Make the two decision rules explicit and pick one. Every company has an unwritten rule about how much certainty it needs before it moves. Two rules in one room look like bad faith on both sides. Written down, they are just a choice.
Get the combined team through one hard shared experience. Not a dinner. A situation with real stakes where they have to decide together and no one side can carry it. That is the executive development work, and for a newly merged senior team it is the fastest route to one team — the two-day format exists for exactly this. If you want to see the mechanics of how the room actually runs, how it works walks through it.
Plant flags and set the 90-day check. Each leader commits to one specific behavior they could change in the combined company. Then schedule the follow-up before anyone leaves. Alignment that goes unchecked at 90 days quietly reverts to two companies wearing one logo.
What It Is Worth When the Teams Actually Merge
At ArcelorMittal, 710 leaders went through Lead the Endurance via Duke Corporate Education. Decisions got 30 to 40% faster. In an integration, decision speed is the whole ballgame — every week a combined leadership team spends re-litigating what the strategy meant is a week the synergy case assumed you were already executing.
At Cadbury, 100% of contracts were renegotiated in 8 weeks instead of the usual 8 months. That is what happens when leaders stop routing every call through a private version of the strategy and start working from one shared picture.
At Bell MTS, revenue grew from $800 million toward $1.4 billion in a single year — leaders across functions finally pulling one direction rather than four.
Your integration plan is probably fine. Most are. It will migrate the systems, close the entities, and harmonize the bands roughly on schedule, and none of that will tell you whether the two leadership teams running the combined company are building the same thing.
Four versions of the strategy will not show up on the dashboard. They show up eighteen months out, in the synergies that were modeled and never landed, and by then everyone has agreed to call it a culture problem. It was an alignment problem, and it was fixable in the first hundred days.
Read next: Cross-Functional Alignment Won't Come From a Reorg