M&A: Leading Change Through Integration โ€” People, Systems and Processes

Mergers & Acquisition

M&A: Leading Change Through Integration โ€” People, Systems and Processes

M&A: Leading Change Through Integration โ€” People, Systems and Processes

About this brief

What is the ECLC? The Executive Council for Leading Change (ECLC) is a global, peer-led community of more than 1,200 enterprise transformation leaders. Members meet in regular virtual roundtables of around 45 executives, held under Chatham House rules, to share what is working, what is not, and how they are handling change.


How Tigerhall fits. ECLC is convened by Tigerhall, the transformation delivery platform for a world of always-on change. Tigerhall turns a companyโ€™s strategy into personalized change journeys for each employee, delivered in the flow of work (Teams, Slack, Outlook, mobile) in 33 languages, with real-time data on where the change is landing and where it is stalling. Leaders own the strategy and the plan; Tigerhall runs the delivery, so a team of two or three can deliver what used to take fifteen to twenty.


What is an executive brief? An ECLC executive brief is a short, anonymised write-up of a single roundtable. It captures what the room discussed, where leaders agreed and differed, and what to do next. Each opens with a summary, then themed sections, then eight key takeaways.


Executive Summary for Leading Change Through M&A Integration: People, Systems and Processes

The deal closes on day one, but the integration is a multi-year change program. Executives from finance, technology, healthcare, consumer goods, media and the public sector compared notes on how integrations quietly lose their footing, how culture gets built on purpose, where AI is already speeding the work, and why systems decisions should follow strategy and process rather than lead them.


Integrations fail slowly and quietly, so the leaders who succeed watch for the soft signals early, treat culture as a workstream from before close, and choose which systems to unify based on why the deal was done.


Early Warning Signals

Chaos in an integration rarely announces itself. Participants named the signals they watch for.

  • โ€œUs versus themโ€ language. Still hearing it around six months in is a red flag. One team banned the word โ€œlegacyโ€ altogether: it is simply one system now.

  • Middle-management turnover. The people who must execute leave when they feel unsupported or unconvinced by the vision.

  • Information hoarding. Fear for oneโ€™s role leads people to hold back what they know.

  • Victim language. โ€œThey are doing this to usโ€ is a cue to ask who โ€œtheyโ€ is, because โ€œtheyโ€ is now โ€œusโ€.

  • Leadership disconnect. What acquired-side leaders say to you versus what they cascade to their teams. Early anxiety about scope and role is human, but unaligned messaging spreads to the front line.

  • A quiet room. Silence is not consent. In one case, leaders from two companies sat on opposite sides of the room at a joint meeting, a tell that they did not yet know one another.

  • Subsidiary chatter. Side conversations across the acquired entity amplify issues.


Course-Correcting Early

  • Shorten feedback loops. Run frequent pulse checks rather than waiting for problems to compound.

  • Use neutral voices. Bring in the change network and influential leaders seen as neutral to surface cross-functional problems.

  • Partner with middle managers. They are where the problems show up first.

  • Assume positive intent. Agree openly that no one is choosing a system or process to prove one side better.

  • Hold hands where it matters. Walk people through what is in it for them and why a choice was made, acknowledging that each option has strengths.

  • Waiting is costly. One parent left an acquisition standing alone for years before integrating it. Unwinding the divide took years more.


Not Every Deal Is the Same

  • Size and intent change everything. A small company joining a large one differs sharply from two sizeable organizations, or from a deal where the target is deliberately left to run independently.

  • Learn from the acquired company. One acquirer is moving away from absorbing targets into its own way of working and toward discovering what they do well, then scaling it across the group.

  • Intentional messiness. A large consumer-goods acquirer left some acquired businesses largely autonomous because they offered advantages it lacked, while consistently emphasising shared values and history. Leadership repeated that day one is the start of the journey, not the end.

  • Exec versus staff tensions differ. Leaders worry about financials, duplicated capabilities and internal cannibalisation. Staff feel the day-to-day gaps in systems, processes and communication.

  • Someone must hold the thread. A 30-60-90 day plan is not the end. The work runs far longer.


Culture Is Intentional

The group was unanimous that culture integration does not just happen.

  • Do the homework before close. Cultural discovery left to the integration phase is already late. Surprises still arise, but you know where people are coming from.

  • Look for microcultures. Management style, decision-making, matrix versus hierarchy and team norms vary within each company. Two โ€œsisterโ€ companies turned out to be very different.

  • Survey both sides before the deal closes. One integration of two media conglomerates ran detailed engagement surveys on both sides, then identified the functional leaders who would carry the new culture forward and equipped them with data and training.

  • Unmanaged culture can turn negative. Without intent, merged groups can form a shared culture of resentment.

  • Stand up an integration management office. It plans each teamโ€™s roadmap, instils company culture in new colleagues, and teaches parent-company staff how to work with them, including buddy systems.


Where AI Is Helping

  • Building the playbook. A finance leader with no integration office and a looming deal used AI to draft an integration playbook by workstream, circulated it for vetting, and launched the office within weeks. It saved an estimated several weeks.

  • Writing product requirements. AI helps draft requirement documents for capabilities needed in the acquired company.

  • Triaging documentation. Teams are flooded with architecture diagrams, process flows and documents. A first-pass summary, played back to the acquired team to verify, saves weeks.

  • Preserving discovery. AI notes from early meetings let a team revisit tax and other questions months later, when people were more willing to share.

  • Audit the targetโ€™s AI. Acquired teams may have built agents that are not in the architecture diagrams. Missing them can degrade customer or user experience.


Systems, Tools and the Human Cost

  • It stalls productivity. Replacing an entire business tool set stops operations and creates the biggest change-management friction. Moving a team from one productivity suite to another is not trivial, and โ€œintuitiveโ€ tools still need training and adoption support.

  • It does not need to be binary. Where people work well in different tools, middleware and back-end integration can let them keep doing their best work. Insist on unification only where it matters.

  • Process first, technology second. One leader learned the hard way that starting with technology is the tail wagging the dog. Re-planning around future-state processes, with function leaders involved, produced better outcomes.

  • Conflicting sources of truth erode trust. Distrusted numbers push people into shadow reporting.

  • Tech debt accumulates fast. A parent company with many acquisitions had multiple CRM instances, two ERPs and two productivity ecosystems. The longer the wait, the harder consolidation becomes.

  • Internal systems can trip the change team. Messy data and the lack of dynamic distribution lists complicate communication in a large, acquisition-built workforce.

  • Set expectations on timelines. In healthcare, moving a newly acquired entity onto the core clinical record is exciting to frontline staff but years away. Managing expectations is hard.

  • Watch change saturation. Finance, HR and technology can still operate in silos even with an integration office. Change fatigue and turnover grow the longer the integration drags.


Tie Systems to Deal Rationale

  • Ask why you bought it. Faster growth, complementary capability or economies of scale each imply a different systems approach.

  • Decouple control systems from growth platforms. The ERP is a backbone, not a growth engine. CRM and data may matter more for cross-selling.

  • Do not forget master data. Product, customer and chart of accounts enable portfolio reporting without a full ERP transformation.

  • Phase it. One acquirer separates the โ€œbusiness integrationโ€ (selling the acquired product, invoicing, recognising revenue and moving people onto the acquirerโ€™s paper, within roughly four months of close) from the deeper transformation that follows. They avoid debating which HR or finance system wins and focus on go-to-market change.

  • Curiosity, empathy and courage. Understand why the target works the way it does, respect peopleโ€™s capacity to change, and resist forcing a change just because a system says so.

  • Changing the acquirer is harder. Expanding the acquired companyโ€™s culture across the parent touches many teams who may not want it.


Key Takeaways

  1. Watch the soft signals. Us-versus-them language, middle-manager attrition and quiet rooms come before the metrics.

  2. Retire the word โ€œlegacyโ€. Language shapes whether people feel like one company.

  3. Do culture homework before close. Survey both sides, map microcultures, and equip future leaders early.

  4. Learn from the acquired company. Its operating model may be better than yours.

  5. Stand up an integration office. One owner per workstream, with a plan that runs well beyond day 100.

  6. Use AI for the heavy lifting. Playbooks, documentation triage and meeting notes, with humans verifying.

  7. Process before technology. Design the future state with function leaders, then pick the systems.

  8. Anchor decisions in deal rationale. Decouple control systems from growth platforms, and unify master data first.

Trusted Change Strategies Straight to your Inbox

Trusted Change Strategies Straight to your Inbox

Tap into the latest insights and proven success blueprints from change leaders around the world.

Tap into the latest insights and proven success blueprints from change leaders around the world.

ECLC logo

Meet Your Peers,
Join the Action.

ECLC logo

ECLC Conference 2026

The AI Summit for
Transformation Leaders

October 8, 2026, 7:30AM ET
City Winery, New York City

How Well is Your Org Activating Change?