The companion article to this one examined M&A IT integration from the technology and programme management perspective. It made the argument, in passing, that the hardest challenges in banking mergers are not technical — they are organisational, cultural and human. This article makes that argument at length. It addresses what actually happens to people when their organisation is acquired or merged, why the standard change management responses are so often inadequate, and what the leadership behaviours and programme structures are that genuinely move organisations from resistance to commitment.
The experience that informs this article spans integrations of very different kinds: the legal merger of two banking entities at BNP Paribas, managing 200+ staff across multiple organisations and countries; the restructuring of an IT division and its subsequent outsourcing to India at Heidelberger Leben, within a six-month programme that affected the careers of everyone in the function; the alignment of 27 European regional companies to a common operating model at ResMed; and the reshaping of an IT operations function at MIG Bank under a cost reduction programme that required significant organisational change. Across all of them, the pattern is the same: the human dimension is not a soft addendum to the programme — it is the programme.
What Happens to People When Their Organisation Merges
Understanding the human response to M&A begins with understanding what a merger announcement actually means to the individuals who receive it. For the people on both sides of a transaction, the announcement creates a period of profound uncertainty that is psychologically damaging regardless of how well-intentioned the communication is. The questions that immediately dominate everyone's thinking — Will I still have a job? Will my role change? Who will I report to? Will my team survive intact? — cannot, in most cases, be answered at the time of announcement. And the uncertainty itself, in the absence of answers, drives the behaviours that most damage integration programmes.
Research on organisational change consistently shows that it is uncertainty, not bad news, that is most corrosive to engagement and productivity. People can adapt to outcomes they dislike if those outcomes are clear and final. What they struggle to sustain is high-quality work in the presence of unresolved questions about their own future — particularly when the announcement signals that someone else is making decisions about that future without their input. The period between a merger announcement and the resolution of individual questions about roles, teams and working arrangements is the most damaging period in any integration from a people perspective, and it is frequently longer than programme planners acknowledge.
"The merger announcement does not create a change management problem. It reveals one that has always been there: the organisation's capacity to sustain trust, performance and commitment under conditions of genuine uncertainty. Programmes that manage this well have usually invested in that capacity before it was needed."
The Four Zones of Response
Across any population of people affected by M&A integration, responses distribute across four zones. Understanding which zone individuals and teams are in at any given point — and what is required to move them toward commitment — is the diagnostic foundation of effective change management.
The goal of a change management programme is not to make everyone enthusiastic — that is neither realistic nor necessary. The goal is to move enough of the population from disengaged and compliant into committed that the integration has the energy it needs; and to address the resistant population honestly enough that their concerns are understood and either resolved or acknowledged, rather than accumulating into an organised opposition that draws energy from the broader population.
The Communication Imperative
Communication in M&A integration is not a workstream that runs alongside the programme. It is a core programme function that must be planned with the same rigour as the technical migration, and it must be led from the top — not delegated to a communications function that produces newsletters while the real decisions are made elsewhere.
The principles that distinguish effective integration communication from the kind that erodes rather than builds trust are specific and consistently learnable. They are also consistently violated by organisations that treat communication as a public relations exercise rather than a leadership responsibility.
Middle Management: The Decisive Layer
The single most important — and most consistently underinvested — element of M&A change management is the preparation and support of middle management. Middle managers are the translation layer between the strategic narrative that senior leadership articulates and the daily working reality that their teams experience. What actually reaches the workforce is not what the CEO says at the town hall — it is what the line manager says the next morning in the team meeting. And what the line manager says depends on whether they themselves understand the direction, believe in it, and feel equipped to explain it.
Middle managers in a merger are simultaneously required to manage their own uncertainty and anxiety about the transaction — their roles and careers are affected too — and to function as the primary change agents for their teams. This is an extraordinary ask. It is not answered by sending them to a one-day change management workshop. It requires sustained investment: regular briefings that give them information before it reaches their teams; forums where they can raise concerns and get honest answers; coaching support to help them have difficult conversations; and genuine inclusion in the integration decisions that affect the people they manage.
The failure mode is common and recognisable: senior leadership is aligned and committed, the change management workstream is producing good communication materials, but at the middle management layer the message is being filtered through individual anxiety and organisational politics into something that undermines rather than supports the integration. People pick up on this immediately. When the line manager's words and body language communicate "I'm not sure this is the right direction" or "I know things I'm not supposed to tell you," the communication programme's investment above that layer is largely wasted.
Cultural Integration: The Difference Between Imposing and Integrating
Every organisation that has existed for more than a few years has developed a culture — a set of shared assumptions, values and behavioural norms that shapes how people work together, how decisions are made, and what is considered acceptable and unacceptable. When two organisations merge, their cultures collide. How that collision is managed is one of the most significant determinants of whether the merged entity functions as an integrated whole or as two parallel organisations operating under the same legal name.
The most common cultural integration mistake is the implicit assumption — rarely stated explicitly but consistently expressed in decisions — that the acquirer's culture is superior and that the acquired entity's culture will naturally give way. This assumption is understandable: the acquirer's leadership team is in control, their processes are becoming the standard, their systems are often the platform. But it produces a specific and damaging outcome: the acquired entity's people, who typically have competencies, knowledge and ways of working that are genuinely valuable, experience the integration as an occupation rather than a merger. The most capable and confident among them leave. Those who remain comply without committing.
The restructuring of the IT and Business Change divisions at Heidelberger Leben — which included outsourcing the IT function to India within a six-month timeline — was one of the most intensive people change programmes I have been involved in. The people affected knew from the announcement that their roles were ending; the question was not whether the change would happen but how it would be managed. What made the difference between a programme that retained the performance and engagement of the affected teams throughout the transition — which was essential, because those teams held the knowledge needed to make the outsourcing work — and one that saw disengagement and early departure was the consistency of three things: honest communication about timelines and processes from the first day, genuine respect for the expertise of the people being displaced, and leadership that was visibly present and accessible throughout the most difficult period. These are not complex things. They are, however, things that leadership often withdraws from precisely when they are most needed — because it is uncomfortable to lead people through change that disadvantages them.
Genuine cultural integration requires curiosity rather than imposition. It requires leaders on the acquirer's side to be genuinely interested in why the acquired entity's culture developed the way it did — what business needs it was designed to meet, what strengths it contains, what it knows that the acquirer does not. Some of what is found will not be worth preserving. Some of it will be genuinely valuable and worth incorporating into the merged entity's culture. The willingness to make that distinction honestly — rather than defaulting to "we will do it our way" — is both ethically better and practically more effective.
Process Harmonisation: The People Dimension
Process harmonisation — aligning the operational processes of two entities into a common target model — is typically treated in integration programmes as a technical exercise: map the current processes, identify the divergences, select or design the target process, implement. What this framing misses is that processes are not abstract workflows — they are the daily practice of real people, and changing them requires changing the habits, knowledge and confidence of those people.
The most difficult process changes in M&A integration are not the complex ones — those get the attention and the training investment they require. They are the ones that appear simple but are, in practice, deeply embedded in the way people work. The approval process that has always worked a certain way. The reporting format that everyone knows. The escalation path that experienced people navigate instinctively. These informal competencies — the accumulated tacit knowledge of how to get things done in a particular organisation — are not captured in process documentation, and they do not transfer simply because the documented process has been updated.
The practical implication is that process harmonisation programmes that rely primarily on documentation updates and training events consistently underperform. The missing element is supported practice: the opportunity for people to try the new process in a supported environment, encounter the difficulties that the training did not anticipate, and develop the practical competence that comes only from doing. In a banking integration context, this typically means extended parallel running of old and new processes, with coaches or process champions available to help when the new process doesn't work as expected — not as a failure of the training, but as the inevitable first step in building genuine competence.
Building the Change Programme: What It Must Contain
An effective M&A change management programme is not a communication plan and a training schedule. It is a structured set of activities across multiple dimensions, each of which addresses a specific aspect of the human dimension of the integration.
What Leadership Must Actually Do
Every element of an effective change management programme depends, ultimately, on what the leadership team does — not what it says, not what the change management function produces, but what the leaders of the integration demonstrably do.
The behaviours that matter most are also, in many cases, the most uncomfortable for leaders operating under the pressure of a complex integration programme. They require leaders to be visible when they would prefer to be working. To have conversations they cannot resolve. To acknowledge uncertainty they cannot eliminate. To listen to criticism they cannot immediately address. And to model the commitment to the merged entity's success that they are asking the broader population to develop.
At Heidelberger Leben, where the people change programme was operating in the context of structural redundancy — not merger ambiguity, but the definitive ending of roles — the leadership quality that made the programme work was presence. Being available. Showing up to the difficult conversations rather than managing them through intermediaries. Treating people who were losing their jobs with the respect they deserved for what they had contributed, and maintaining that respect consistently rather than only in formal settings. None of this required extraordinary talent. It required the discipline to prioritise human engagement over the other pressing demands of a complex programme — which is harder than it sounds, and rarer than it should be.
Questions for Integration Leaders
- Have you mapped your affected population across the four zones of response — and do you have specific plans for each zone rather than a single programme for everyone?
- Is your integration communication plan designed to acknowledge uncertainty honestly, with specific commitments to resolve open questions by named dates?
- Have your middle managers been briefed before their teams, given the information they need to answer likely questions, and offered ongoing support for the difficult conversations they will face?
- Has the leadership team explicitly discussed and aligned on the integration narrative — not the press release version, but the genuine account of why this integration is the right direction and what it will require?
- Does your process harmonisation programme include supported practice as well as training — giving people the opportunity to develop real competence in new processes rather than just documented understanding?
- Are the resistant voices in both organisations being engaged rather than suppressed — with genuine curiosity about the concerns behind the resistance and genuine willingness to act on those that are legitimate?
- Is change management embedded in the integration programme's governance as a core workstream — with its own reporting, its own KPIs, and its own escalation path — rather than treated as a communications and training support function?
- Is the senior leadership team visibly present and accessible throughout the most difficult periods of the integration — or are those periods precisely when leadership withdraws to focus on programme management?
Conclusion: The Integration Lives or Dies in the Room Where People Work
The business case for a banking merger is written in conference rooms and law firms. The synergies are modelled in spreadsheets. The technical integration is designed by architects and delivered by programme teams. But the merger itself — whether it actually becomes a coherent, functional organisation capable of delivering the value it was predicated on — is determined in a different place entirely: in the daily working relationships, conversations and decisions of the thousands of people who come in every morning and choose, repeatedly, how much of themselves to invest in making the merged entity work.
That choice — the accumulated individual decisions to commit, comply, resist or disengage — is influenced by leadership behaviour more than by any programme activity. Leaders who are honest about uncertainty, present during difficulty, curious about the cultures they are integrating, and consistent in the respect they show for the people being asked to change are the most powerful change management instrument available. No communication plan, stakeholder engagement programme or training curriculum replaces them.
The technical integration can be planned, resourced and executed. The human integration must be led. And leading it well — in a banking merger, with its regulatory pressures, tight timelines and high stakes — is one of the most demanding things an IT and transformation leader is ever asked to do.