Your Company Just Doubled in Size. What Happens to the Culture?
The acquisition announcement says the company is entering an exciting new chapter.
On Monday, someone needs to approve a customer exception. One team calls the plant manager. The other submits a request through three levels of leadership.
Both believe they are doing it correctly.
Welcome to the exciting new chapter.
When a merger or acquisition suddenly doubles your organization, you inherit more than people, products, and locations. You bring together different understandings of authority, accountability, trust, and what it takes to succeed.
And you have a second challenge: the combined organization is now operating at a scale that may stretch the habits of both companies.
You are bringing two histories into a future neither organization has worked in before.
That is where post-merger culture integration needs to begin.
Start with what the deal needs to deliver
Before deciding what the combined culture should look like, clarify what the acquisition is supposed to make possible.
Are you expanding production capacity? Buying technical expertise? Entering a new market? Bringing complementary products to the same customers?
The answer should shape your integration decisions.
If you acquired a company because it responds quickly to specialized customer needs, routing every decision through your existing approval structure deserves scrutiny. You could slow down the capability you paid to acquire.
If the deal depends on coordinating production across facilities, however, incompatible planning practices may need to change.
The question is: which ways of working will help the combined organization deliver the value of this deal?
McKinsey’s guidance on culture and M&A connects cultural priorities to transaction value, including the behaviors and management practices the new organization needs to succeed.
That gives the work a business purpose: protect valuable capabilities and help the larger organization perform.
Assess both cultures… including your own
The acquiring company can easily become the unexamined standard. Its processes become the default, while the acquired company gets assessed for how well it will fit.
Who wrote the check has become an answer to which way of working is better.
It is worth questioning that.
A useful culture assessment examines how work actually happens across both organizations. Ask employees, managers, and leaders:
Which decisions can you make without asking permission?
What happens when someone raises bad news?
When do people bend a process to keep work moving?
What gets rewarded when speed, quality, and cost compete?
What would you hate to lose through this acquisition?
What would you be relieved to leave behind?
Ask for examples. Compare perspectives across functions, locations, shifts, and levels. Interviews, focused group conversations, observation, and existing data can give you a fuller picture than leadership impressions alone.
Two manufacturers may both describe themselves as quality-driven. At one, stopping the line earns support. At the other, employees learn to keep production moving and sort out defects later.
The shared value sounds reassuring. The different responses tell you where integration work is needed.
Compare how work happens, and how much those differences matter
A framework shared with me during a recent networking conversation offers a useful way to make this comparison more concrete. It examines the expectations and practices that shape work in each organization.
The following areas to explore and questions help structure that comparison:
-
How are decisions made: through group agreement, employee input followed by a leader’s decision, or leadership direction?
-
Where can employees exercise judgment, and where do they need direction or approval?
-
What information reaches employees routinely, and what is restricted to particular roles?
-
How do people balance analysis with acting on the information currently available?
-
How much room is there to experiment, and what happens when an experiment goes wrong?
-
What motivates people and signals that their contribution is valued?
Alongside comparing practices, ask how much each way of working matters to the people and organization involved.
A difference in approval practices might affect customer response time. Another difference might be a local preference that does not interfere with shared work. Understanding the significance of each helps leaders decide where change is worth the disruption.
Also look for variation within each company. If employees describe the same practice very differently, investigate what varies by team, site, shift, or leader. A company average can hide those experiences.
Use examples to understand what the differences mean. Then connect the findings to the purpose of the deal and decide what to preserve, share, or redesign.
Decide what to preserve, share, and redesign
A combined organization needs deliberate choices about where common practices matter and where differences should remain.
Some practices may need to be shared across the business: safety expectations, quality requirements, financial controls, or escalation rules.
Others may be valuable precisely because they are local: specialized customer relationships, technical routines, or ways of coordinating within a particular facility.
And some practices may need a fresh design because neither company’s approach will serve the larger organization.
Consider a founder who previously approved every major customer commitment. Doubling the business could turn that familiar habit into a queue. The value worth preserving might be responsiveness; the mechanism now needs to include clear authority and decision boundaries for other leaders.
That is organizational alignment work with cultural consequences.
For each major practice, ask: What purpose does this serve? Where does it create friction? What does the larger organization now require?
Make power and participation explicit
An acquisition changes whose judgment carries weight.
Employees will notice who gets leadership roles, whose systems become standard, which locations executives visit, and whose concerns receive a response.
A welcome message cannot resolve an integration process that consistently treats one company’s knowledge as more credible.
Bring people from both organizations into the decisions that affect their work. Include respected informal leaders and employees who understand customer relationships, production constraints, and the workarounds keeping things moving.
Be clear about their role. Are they providing input, developing recommendations, testing options, or making a decision?
Participation does not require consensus on everything. It does require an honest explanation of what people can influence—and evidence that their knowledge mattered.
Give managers something useful to say
Employees are trying to understand what the deal means for their jobs, authority, relationships, and future.
Managers need enough context to handle those conversations. Give them:
Confirmed decisions and the reasons behind them.
Open questions, with named decision owners.
A date for the next update.
A route for escalating concerns they cannot resolve.
Be precise about uncertainty. If reporting lines are still being designed, say so. If a decision is final, explain it without presenting it as a discussion.
Avoid promising that nothing will change when the purpose of the deal requires change. Credibility depends on whether the next announcement matches what people were previously told.
McKinsey’s integration planning guidance identifies role clarity, decision-making, talent, performance management, and customer focus as practical cultural priorities.
Those priorities help turn an acquisition story into usable expectations.
Build the culture into everyday work
Once leaders identify the behaviors the combined organization needs, examine what will encourage them.
If teams are expected to collaborate across locations, how will goals and incentives support that? If decisions should move closer to customers, who now has authority? If quality concerns should surface earlier, how will leaders respond when someone raises one?
In CulturePop’s post-acquisition work with a growing manufacturer, leadership and employee involvement helped define actionable values and connect them to hiring, performance, and daily decisions.
Those connections make cultural intent consequential.
Choose a small number of priority changes, give each an accountable owner, and make room for the work. Integration responsibilities need time and resources alongside the job of keeping the business running.
Watch whether work gets easier
A practical early plan should establish what needs immediate clarity, where further listening is required, and which changes can be tested first.
You might start with one shared customer handoff, one approval process, or one recurring cross-site decision. Learn from it before expanding.
Track whether decisions move faster, handoffs become clearer, customer commitments hold, and employees understand their responsibilities. Watch retention in critical roles and look for differences between locations or legacy companies.
Keep listening as you act. Explain what changed because of employee input and what did not, including why.
Culture integration continues well beyond the announcement and the first round of workshops.
The larger organization becomes real through repeated choices: who gets heard, how disagreements are resolved, what leaders protect, and what they are willing to change.
When your company doubles in size, what deserves to come with you, and what will you need to build together?
CulturePop helps leaders work through those choices, connecting culture, leadership, and ways of working so growth produces clearer decisions and stronger experiences. Let’s talk about what your integration needs next.
