Culture change after a merger

There is a moment that leaders who have been through a merger will recognise. The structural integration is done. The org chart has been drawn. The systems have been migrated - or at least the migration is underway. The branding is unified, the leadership team is in place, and the deal, by any formal measure, is complete.

And yet it still feels like two organisations.

Two sets of assumptions about how decisions get made. Two ways of running a meeting. Two defaults for who gets consulted before something moves forward. People still referring to "how we used to do it at..." months or even years after the merger closed. Not out of resistance, but because nobody designed what would replace those habits.

This is one of the most common experiences in organisational life, and one of the least well served by the integration process that's supposed to address it.

What merger integration typically covers

Modern merger integration is sophisticated. The financial integration, IT migration, governance alignment, structural design, TUPE processes - all of it demands serious expertise, and it is usually well covered. Integration plans run to hundreds of pages. Programme management offices coordinate dozens of workstreams. Timelines are tracked, milestones are hit, and the operational mechanics of bringing two organisations together receive the attention they deserve.

Culture is usually mentioned. It appears as a workstream, or a strand within the people and communications plan. There might be a values exercise, an engagement survey, a series of town halls where the new vision is shared. These are not bad things. They are just not the same thing as designing how two ways of working will find each other.

The result is a pattern that keeps repeating across sectors: the operational integration completes, the structures are in place, and the organisation still does not feel like one. Not because the integration failed, but because the part that determines whether people work as one organisation - the culture - was managed rather than designed for.

The pattern behind the pattern

Research from MIT Sloan Management Review, drawing on a quarter-century of S&P 500 data, found that 46% of all M&A deals are ultimately undone - and not quickly. The unravelling happens gradually, over years. Mercer's global research puts it more specifically: 30% of mergers that fail to meet their financial targets attribute that failure directly to cultural misalignment.

What makes these numbers worth pausing over is not the scale of failure. It is the consistency of what people point to when they explain it. Cultural clashes. Integration fatigue. People from both sides waiting for the other to adapt. Key talent drifting away. Decision-making that stalls because nobody is sure whose process to follow any more.

Everyone involved in mergers knows this. It appears in every post-deal review, every integration retrospective, every honest conversation between leaders who have been through one. Culture is the acknowledged cause of underperformance. And yet it remains the dimension of integration that receives the least design attention.

This is not because leaders do not care about culture. It is because the tools and processes available for integration are designed around things that can be project-managed - systems, structures, finances, governance - and culture is not one of those things. Culture does not respond to a project plan, a set of milestones, or a communications campaign. It emerges from something deeper.

What culture after a merger really is

Here is a different way of seeing it.

Culture is not a separate thing from the operational integration. It is not a workstream that sits alongside the IT migration and the financial consolidation. Culture is the medium through which all of those things either work or do not. It is how decisions get made, how people collaborate across old boundaries, how conflict gets surfaced or buried, how the organisation learns and adapts. When two organisations come together, two sets of these patterns meet - and what emerges from that meeting determines whether the merger creates something genuinely new or just puts two ways of working under one roof.

This is why values workshops and engagement campaigns - however well intentioned - do not close the gap on their own. They try to change culture directly, by telling people what the new values are and hoping behaviour follows. But culture does not work that way. It emerges from the conditions people work within: the decision-making structures, the performance systems, the collaboration patterns, the everyday operational realities that shape how work happens.

After a merger, those conditions are in flux. Two sets of decision-making habits are colliding. Two approaches to risk, to consultation, to autonomy are trying to coexist. The silos that form are not just departmental - they run along legacy lines, separating people who technically work for the same organisation but still operate from different assumptions about how things are done.

When those conditions are designed for - when someone asks "how will decisions be made in the new organisation, and what will make cross-boundary collaboration feel natural?" - culture follows. When they are left to sort themselves out, the merger stays on paper for much longer than anyone planned.

What changes when culture is designed for

When the culture dimension of a merger is given the same design attention as the structural and operational dimensions, something shifts. Not immediately, and not through a single programme, but through a series of deliberate choices about how the new organisation will work.

It starts with understanding how both organisations work in practice - not just their structures, but their habits, their rhythms, the things people value about how they do their work. Not to judge one side's approach as better, but to see what each organisation brings and what needs to be deliberately shaped in what comes next.

It means creating the conditions for shared identity to form, rather than waiting for it to emerge on its own or imposing one side's culture on the other. In one housing association merger we worked on, the guiding principles for the new organisation were not drafted by the leadership team and cascaded down. They were drawn from what people across both legacy organisations - and the customers they served - said mattered most. Sixteen percent of the workforce volunteered to join cross-departmental action groups to bring those principles to life. Not because they were told to, but because the process was designed to make their involvement meaningful.

The principles were then woven into performance management, supported by practical manager toolkits, and embedded into how teams worked together across old boundaries. Culture changed not because people were told what the new values were, but because the systems and structures they worked within were redesigned to make new patterns of working natural.

This is the difference between integration that creates uniformity and integration that creates unity. Uniformity means everyone doing things the same way - usually the way the larger or dominant partner already did them. Unity means everyone working toward the same things, in ways they helped shape. Uniformity is faster. Unity is what makes a merger integration stronger than what existed before.

The question beneath the question

Most merger integration plans ask: how do we bring these two organisations together? That is the right question, but it is incomplete.

The deeper question is: what kind of organisation do we want to become - and what conditions will help it get there?

That question cannot be answered by a project plan. It requires a different kind of attention - to patterns, to habits, to the invisible architecture of how work happens. It requires designing for culture as a living system, not managing it as a workstream.

For any organisation navigating a merger, this is the dimension that determines whether the deal delivers on its promise. Not in the first hundred days, but in the years that follow - when the programme office has disbanded, the integration milestones have all been ticked, and the real test begins: whether two groups of people can work as one.