How Do You Build One Culture After a Merger Without Erasing Both?
How to build one culture after a merger without erasing either organisation, by preserving strengths and creating shared decision rules.
By Stuart Andrews
How Do You Build One Culture After a Merger Without Erasing Both? My answer is direct: One culture after a merger is not a forced blend. It is a set of shared choices about how the combined organisation behaves when the interests of teams collide. HBR’s guidance makes the employee integration experience central. People decide whether a culture is real by watching who gets heard, promoted and protected.
one culture after a merger
I start with a culture inventory: strengths to keep, habits to retire and tensions that need a new rule. The new culture is built through decisions. Which customer promise wins when capacity is tight? How is disagreement handled? What does a good escalation look like? McKinsey describes operating model design as including structure, process, talent and behaviours. Culture work should be connected to those choices rather than run beside them.
What the merger is really asking of people
The new culture is built through decisions. How is disagreement handled? What does a good escalation look like? A slogan cannot answer those questions. A shared-choice model can, because it connects values to a visible operating behaviour. Leaders should create mixed teams to solve real integration problems. The work produces relationships and evidence that a workshop alone cannot create.
Find the seams between the two cultures
A slogan cannot answer those questions. The CEO has to acknowledge what each organisation is proud of and what will change. Pretending the histories are identical makes trust harder.
When integration creates avoidable friction
Progress is measured through observed decisions, cross-team confidence and the speed of resolving friction, not by a survey score alone.
Rituals that help people work together
A unified culture keeps both organisations’ dignity while creating a new pattern of choices that neither could have produced alone.
Signals that trust is moving
Decisions that should stay local
The first cultural choice after close
A combined culture without erasure
A unified culture keeps both organisations’ dignity while creating new patterns of choice that neither could have produced alone. That is the question I would put to an integration board.
Bring the people responsible for a customer promise around one decision the merged business must make. Set out the facts, name the constraint and agree what would have to hold for the preferred choice. Then examine the consequences for managers, customers, data, culture and the board.
A post-merger culture conversation should begin with a concrete decision, such as which customer promise takes precedence when the two legacy systems disagree. People learn the new culture by watching that choice. The language in the values deck matters less than the explanation leaders give afterwards and the behaviour they reward in the following week.
My working method is a three-column inventory before designing integration workshops: preserve, retire and create. Preserve captures strengths that made each organisation effective. Retire names habits that create friction or conceal risk. Create describes the behaviour neither side has had to practise before. The third column is where a shared culture starts.
Acquired employees notice fairness through small signals: whose process is treated as the default, who gets invited into decisions and whether leaders can admit what they do not yet understand. A mixed integration team can surface those signals faster than a central culture campaign because it has to solve real work together.
The first operating rules should cover disagreement, escalation and customer impact. Those rules give people a safe way to act while the combined structure is still moving. They also prevent culture from becoming a personality contest between legacy leaders.
A unified culture does not require identical rituals. One team may keep a useful practice that another does not adopt. The test is whether both groups can explain the shared principle behind a decision and recognise how it applies in their own work.
I would review cultural integration through observed choices, regretted attrition, cross-team trust and the speed of resolving friction. A survey can help locate questions, but it cannot prove that the new culture is carrying the operating model.
Agree how the combined business will handle one customer promise. Give someone ownership and observe the next real handoff. The finding matters when it changes an integration decision, not when it simply fills another culture slide.
In this article’s context, I would protect a trusted practice while its value is tested.
In this article’s context, I would make promotion and recognition evidence of the new culture.
In this article’s context, I would give acquired employees a route into consequential decisions.
In this article’s context, I would treat disagreement as a design input rather than disloyalty.
For one culture after a merger, watch the first decision where the two organisations have to rely on one another. Note whose evidence carries weight, where the handoff slows and what local practice deserves protection. Ask an outsider to challenge the interpretation.
Carry those observations into the integration review. Ask what improved, which exception exposed a hidden assumption and who can act on it now. A shared culture is becoming real when the behaviour survives beyond the deal team.
For How Do You Build One Culture After a Merger Without Erasing Both, I would use the Leadership Capability Architecture framework to make the decision rights and routines visible, then check the practical intelligence layer in CapabilityAI. The relevant service context is this implementation pathway. Those links let a reader move from this specific question into a working diagnostic.
The implementation detail: How Do You Build One Culture
One story in The Leadership Shift concerns a global financial organisation divided by cultural friction between business units. Motivation was falling, intellectual property was leaking and several client transitions had already failed. The answer was not a slogan about unity. It was clearer goals, leadership behaviour that rebuilt trust and centres of excellence that gave people a shared place to work through the change.
The merger becomes real in the moments that do not make the integration plan. A customer escalation, a promotion decision and a missed handover reveal which history still carries more weight. The first question is leaders to review those moments together, with the people who had to make the call. That conversation surfaces unwritten rules without turning culture into a survey score. The next step is a small, visible choice made on the basis of the combined organisation’s needs. Repeated choices of that kind build trust faster than a launch event.
A merger creates two versions of ordinary work before it creates one culture. People bring different approval habits, meeting times and definitions of a finished job. Put those differences on the table. They are operating facts, not signs that one side cares more than the other.
The first integration conversations should involve the people who answer customers, run the close and solve exceptions. Ask them to show where a request changes hands. Those handoffs reveal which practices need to be combined and which should remain local while the new organisation learns.
A shared culture statement will not settle a dispute about authority. A decision rule might. Write down who decides, who must be consulted and what evidence is expected. Use the rule on one live issue, then adjust it when the work exposes a gap.
The acquired team also needs a way to keep useful knowledge visible. Name the practice worth protecting, the reason it works and the conditions under which it can travel. Do not call every difference a best practice. Some are responses to a customer, a regulation or a history that the parent company does not yet understand.
Integration is moving when people can explain the new way of working without pretending the old way had no value. The test is practical: fewer escalations, clearer decisions and enough trust for someone to say that a promised change will not work.
People need a way to challenge an integration choice without being cast as disloyal. Use a short review after each major handoff. Ask what became easier, what became slower and which local practice should stay for now. The answers will be uneven, and that is useful information.
The new organisation does not need one accent, one meeting style or one story about the past. It needs enough shared rules for work to move and enough respect for local knowledge that people keep telling the truth about what is happening.
Integration improves when the new rules are tested in the work that people already care about. Choose a customer promise, a month-end task or a safety check. Let both teams show how they would handle it, then agree the rule that removes confusion without erasing useful judgement. Record the reason for the decision. Six weeks later, revisit the same case and ask whether the rule helped. That second conversation is where trust is built. People can see that their knowledge changed the system, and leaders can see where the system still asks for local judgement. A merger becomes more stable when th
The practical aim is not sameness. It is a shared way to decide, with enough room for the knowledge that made each side successful before the deal.
A merger also changes the informal routes through which people get help. One team may ask a colleague in the next room; the other may open a ticket or wait for a weekly meeting. Map those routes before imposing a single process. Keep the route that resolves the customer’s problem fastest, then make the ownership visible to both groups. The detail can feel small, but it determines whether people share information or build parallel workarounds. Review the map after the first busy month and change the rule where it creates delay.