And the Three Change Leadership Disciplines That Prevent It.
KPMG found that 83% of M&A deals failed to boost shareholder returns. A recent 2025 survey from Global PMI Partners shows 70% of executives now rate their latest deals as successful. Both numbers can be true at the same time, because the gap between experienced and inexperienced acquirers is widening, not closing.
Companies that have figured out integration are getting better at it. Companies that haven’t are still failing at the same rates they always have. I led integration change management across more than 40 acquisitions. The lesson I keep coming back to is this: integration doesn’t fail because the synergy model was wrong. It fails because the acquiring organization doesn’t understand itself well enough to absorb what it’s buying.
Know Yourself Before You Know the Target
Most integration playbooks start with the target. What are we buying? What’s their operating model? How do we slot them in? These are important questions. But they’re the wrong place to start.
The right place to start is your own organization. How do your business units actually make decisions? Where are the fault lines between divisions? Who has real authority versus nominal authority? What happens when a cross-business-unit initiative requires cooperation from leaders who don’t share a P&L?
Several years ago at IBM, this question became unavoidable. IBM’s primary acquisition targets were software companies, and since IBM was structured into three business units at that time (Software, Technology, and Services), it was fairly straightforward to integrate a software acquisition’s operating model and culture into IBM’s Software Group. The playbook worked. The receiving business unit understood the target, had relevant expertise, and could absorb the people, products, and processes without too much friction.
The challenge arose when the target didn’t fit neatly into a single box.
Consider a target company, typically valued at $50–500M, that had software, services, and hardware. Since the Software Group was funding the acquisition, they took the lead. But they had less interest in and less knowledge of the target’s other business and operating models: the services practice, the hardware line, the channel relationships. These were often critical to the target’s success and to the synergy case, but the acquiring business unit wasn’t equipped to integrate what it didn’t fully understand.
Anyone who has worked in a large enterprise organization can imagine what happens next. The software business is integrated well. Services and hardware components are neglected, misallocated, or forced into structures that don’t fit. Key talent from those parts of the target leaves. Revenue deteriorates. The synergy case erodes, not because the deal was bad, but because the acquiring organization’s internal misalignment made it impossible to execute cleanly. Worse, the acquiring company appeared as incoherent, disparate parts to the very people it was trying to retain and integrate.
The Intervention: Leadership Alignment Before Integration Planning
When I assumed leadership of IBM’s acquisition integration change management practice, one of the first things I introduced was something that had become commonplace in IBM’s external consulting practice but had never been applied to our own integration work: structured leadership alignment.
The concept is straightforward. Before you design the integration plan, before you assign people to workstreams, build timelines, or model synergies, you bring the leadership of each affected business unit together and align them on the areas most critical to the success of the deal. Not a town hall. Not a briefing. A working session where leaders from Software, Services, and Technology sit in the same room and confront the reality that this acquisition affects all of them, that their individual decisions will either reinforce or undermine the synergy case, and that the target’s people are watching to see whether IBM can act as one company or three.
Bain & Company’s research on change management in merger integration supports this approach directly. Their work across hundreds of integrations found that most companies significantly underestimate the effort required to build a joint vocabulary between merging organizations. Senior leadership must invest considerable time learning one another’s language as a first step toward alignment. In our experience, this was exactly right, but the vocabulary gap wasn’t just between the acquirer and the target. It was between the acquirer’s own business units, who often had not collaborated on anything this operationally complex unless they had been through an enterprise software implementation, a topic for another article.
Over time, the results spoke for themselves. The case for leadership alignment became so clear that the question shifted from whether to do it to when in the process we could start. The more experience we gained, the earlier we moved these sessions, eventually conducting them during due diligence, well before close. This gave leadership the context to have more informed conversations with targets about the deal’s value levers and what was needed to protect them. It also sent a powerful signal to the target: this acquirer has its act together.
Design the Operating Model Before You Merge the Org Chart
McKinsey’s February 2026 research on operating model design during mergers found that organizations reporting effective implementation of the combined operating model post-merger are significantly more likely to meet or exceed both cost and revenue synergy targets. They define operating model as four elements: structure, process, talent, and behaviors.
Most acquirers focus almost exclusively on structure, the org chart. Who reports to whom? Which functions consolidate? Where do we eliminate redundancy? These are necessary decisions, but they’re insufficient. Structure without process redesign means you’ve moved boxes on a page while the actual work still flows through the old channels. Structure without talent alignment means you’ve assigned new roles without equipping people to succeed in them. Structure without behavior change means the new org chart looks different but operates exactly the same way.
At IBM, we experienced this directly when eliminating 4–6 management layers across the enterprise. The structural change was dramatic, but the real transformation was in redesigning decision rights, adjusting spans of control, and rebuilding the governance rhythms that determined how work actually got done. The same principle applied to every acquisition: the integration plan had to address not just where the target’s people would sit, but how the combined organization would actually operate day to day.
Organizations that bolt an acquisition onto a pre-existing operating model capture at most 20% of available value. Sustainable integration value requires deliberate redesign of decision rights, workflows, and organizational structure, ideally designed before close and implemented with discipline in the first 100 days.
Answer the “What About Me?” Question First
EY’s research on integration leadership identifies a quality that sounds simple but is remarkably rare in practice: the ability to set the tone of the integration, measure employee sentiment regularly, and take steps to shift opinion as needed. The most effective integration leaders are well-respected individuals who can ground senior leadership around shared guiding principles and inspire teams that have never collaborated to work toward a shared goal.
In my experience, the single most important thing an integration leader can do in the first 48 hours is answer one question for every employee in both organizations: What does this mean for me?
Not “what does this mean for the company.” Not “what does this mean for our strategy.” What does this mean for me: my role, my team, my manager, my career, my daily work.
Until that question is answered credibly, nothing else matters. Employees will not engage with a new vision, adopt new systems, or collaborate with new colleagues while their fundamental question remains unanswered. The information vacuum gets filled with rumor, anxiety, and the quiet updating of LinkedIn profiles. BCG’s research confirms this: over half of all M&A deals fail to deliver a return on value, and the human factor, not the financial model, is the primary driver.
The mistake most integration teams make is treating this as a communications problem. It isn’t. It’s a leadership problem. Town halls with generic reassurances (“we value everyone”) don’t answer the question. What answers the question is direct, honest, role-level communication: here is what’s changing, here is what isn’t, here is the timeline, and here is what we don’t know yet but will tell you as soon as we do. The leaders who do this well build trust that carries the integration through its hardest months. The leaders who don’t lose their best people before the integration has a chance to succeed.
The focus above is on the persona of “employee,” but equally important is the acquisition’s top leadership. These leaders often have a particular DNA that is averse to mature organizations with well-defined policies, processes, and broad footprints. They would often rather create and launch the next venture than operate inside a large enterprise. So how do you motivate the very people who made the acquired company successful to stay long enough to ensure their formula for success is preserved?
You certainly don’t simply “slot them in” to your blue-chip company expecting them to be grateful for the opportunity, which was the typical approach. While we often neglect this question for senior leaders, assuming their monetary reward should be sufficient, the same “What about me?” question applies to them. Beyond a roadmap of incentives artfully designed by HR, being intimately familiar with each leader’s personal goals and interests, and providing them with opportunities only a larger organization can offer, is where retention begins. One would be surprised by how divergent a leader’s next ambition can be after achieving the goal of being acquired.
Measure from Day Zero, Not Day 100
The final discipline, and the one most often skipped, is measurement. While IBM’s integration programs were (and presumably continue to be) strong at ensuring adequate baselines before the integration starts, many organizations I benchmarked and have worked with launch into execution, and six months later, when the board asks whether the deal is delivering value, the integration team scrambles to assemble a narrative from whatever data happens to be available.
This is how good integrations get defunded. Not because they’re failing, but because they can’t demonstrate they’re succeeding. The CFO sees cost but can’t see value. The board sees activity but can’t see outcomes. The integration team knows things are working, but can’t prove it in language that survives a board presentation.
The solution is to build the measurement architecture before the integration begins, ideally during due diligence or immediately post-signing. Establish baselines for the metrics that matter: revenue by product line, customer retention, employee retention in critical roles, time-to-productivity for integrated teams, and synergy capture against the deal model. Track leading indicators monthly, not just lagging indicators quarterly. Report in the CFO’s language, not the integration team’s language.
This discipline transforms the integration from a cost center that periodically asks for patience into a value-creation engine that demonstrates progress in credible, quantified terms. It also creates accountability, because when dimension scores are visible, leaders can’t hide behind vague assertions that “things are going well.”
Integration Is a Leadership Discipline, Not a Project Plan
Acquisition integration is a transformation. And like all transformations, its success depends not on the quality of the plan but on the quality of the change leadership behind it. The three disciplines (leadership alignment before integration planning, operating model design before org chart design, and measurement from day zero) are not new concepts. But they are consistently underestimated, under-resourced, and under-prioritized by organizations that treat integration as a project management exercise rather than a leadership challenge.
The organizations pulling away from the pack, the ones showing up in that 70% success rate, have institutionalized these disciplines. They don’t reinvent integration with every deal. They build repeatable capability, invest in dedicated teams, and treat each acquisition as an opportunity to refine their approach. They understand that the most important integration work happens inside their own organization before it ever reaches the target.
The 83% failure rate is not a law of nature. It’s the result of organizations that haven’t yet learned what experienced acquirers already know: integration is a change leadership discipline, and it can be built, measured, and improved like any other.
_________________________________________________________________________________
Sources
Bain & Company, “Change Management in Merger Integration,” Bain.com, 2024.
Boston Consulting Group, “The M&A; Value Creation Challenge,” BCG.com, 2024.
EY, “Integration Leadership: What It Takes to Lead a Successful Merger Integration,” EY.com, 2024.
EY, “Nine essential qualities of an M&A integration leader.” EY Insights — Mergers & Acquisitions, 2025.
Global PMI Partners, “State of M&A; Integration Survey,” 2025.
KPMG, “Global M&A; Report: Unlocking Deal Value,” 2023.
McKinsey & Company, “Designing Operating Models for Post-Merger Integration,” McKinsey.com, February 2026.
Marden Fitch, “AI Transformation Readiness Index (ATRI™) Framework,” 2026.
_________________________________________________________________________________
