The deal closed six months ago. Why are you still running two companies?

“Which company were you from?”

Six months after an acquisition, employees still ask this question.

They know which expense rule applies to a legacy team. They know which leaders expect a detailed discussion before a decision and which leaders regard that discussion as resistance. They know that the same customer request will receive a different answer depending on the business unit handling it.

The organisation chart has one company name at the top. Daily work has preserved two companies underneath it.

This can happen even when the integration programme is on schedule. Legal entities have been combined. Leaders have been announced. Systems are being migrated. Synergy numbers are reported every month. The task list is moving while the operating model remains unsettled.

Integration begins with the reason for the deal

A deal intended to gain scale should produce different operating choices from a deal intended to acquire a specialised capability. A geographic expansion may need local freedom. A consolidation may need common processes quickly. A talent acquisition may lose much of its value if the acquired team is absorbed into the buyer’s usual structure.

The 2026 McKinsey work on post-merger operating models recommends defining both an end-state model and any interim model required to reach it. It covers structure, process, talent and behaviour because all four affect whether the combined company can deliver the deal rationale.

The deal rationale is often understood by the transaction team and described to employees in broad terms. Integration decisions then get divided among functions. Finance combines reporting. HR harmonises policies. Technology plans migrations. Business leaders pursue synergies. Each stream can make sensible choices and still create an incoherent company.

Four questions help keep those streams connected.

1. What must the combined company be able to do?

Avoid starting with the boxes. Start with capabilities.

Does the combined company need to serve customers across both offerings? Does it need one view of capacity? Must it price consistently? Is local market knowledge central to the value case? Which capability from the acquired business needs protection?

Write the answers in operational language. “Become one company” is an aspiration. “Present one account plan to the top 50 shared customers within six months” can guide decisions.

Once the capabilities are clear, leaders can judge which processes and roles should be common.

2. Which decisions must be made in the same way?

Complete standardisation is rarely necessary. Decision consistency is often more important.

Two business units may keep different delivery processes and still need one rule for accepting contractual risk. Regions may retain local hiring practices and still use common criteria for senior leadership roles. Product teams may use different methods and still follow one portfolio investment process.

Identify the decisions whose inconsistency would damage the deal value, customer experience, risk position or employee trust. For each one, define:

• The owner in the combined company

• The people who provide input

• The criteria that guide the choice

• The threshold for escalation

• The date when the new rule begins

• The treatment of existing commitments

That last item prevents a common source of resentment. People can accept a new rule more easily when leaders acknowledge contracts, promises and expectations created under the old one.

3. Where is variation useful?

Acquirers often describe their own practices as standards and the acquired company’s practices as variation. The language gives the answer away before the analysis begins.

Ask which method produces value in its context. A local sales practice may preserve important customer relationships. A specialised engineering team may need different career paths. A regional operation may face different talent or regulatory conditions.

Local freedom also needs boundaries. What outcome must remain common? Which risks cannot be local? When does an exception require review? How will a successful local practice be considered for wider adoption?

This is the dilemma of standardisation and flexibility in a very practical form. The answer will differ across processes. Declaring that the company will “take the best of both” postpones the work of deciding what best means.

4. Which systems will reinforce the new choices?

A leadership team can agree on collaborative behaviour and retain incentives that reward unit performance alone. It can announce empowerment while keeping every financial approval at the centre. It can ask people to share talent while succession decisions remain within legacy groups.

Employees believe repeated experience. They notice who gets promoted, how exceptions are treated, which numbers dominate reviews and what happens when a leader takes a decision within the stated boundaries.

Examine the systems that carry the new operating model:

• Goal setting and performance reviews

• Hiring and promotion criteria

• Customer ownership and revenue credit

• Investment approvals

• Leadership meeting agendas

• Escalation routes

• Recognition and incentives

• Policies that affect day-to-day judgement

Each system is a message about how the combined company works.

Five ways two companies survive inside one structure

The org chart is treated as the operating model

Reporting lines answer who reports to whom. They do not explain how customer, product, talent and investment decisions cross those lines.

Leaders are announced before mandates are agreed

A title gives a leader status. It does not settle which decisions moved with the role, which stayed elsewhere and how legacy leaders will participate.

Values are discussed separately from work

A values workshop can produce useful language. The effect appears when the language changes a hiring decision, a customer promise, a review conversation or an escalation.

The acquirer’s method becomes the default

The larger company usually has more policies, systems and people assigned to the integration. Its method wins many choices through momentum. Useful capabilities in the acquired company can disappear without ever being rejected deliberately.

Progress is measured through completed tasks

System migrations and policy harmonisation are easy to count. Decision quality, cross-legacy cooperation and clarity of accountability require closer observation. A green task tracker can coexist with frustrated customers and duplicated work.

Keep an integration dilemmas register

An integration programme usually has a risk register and a decision log. Add a dilemmas register.

Record the recurring tensions that require a leadership choice:

• Common customer standards and local relationships

• Rapid synergy capture and business continuity

• Retaining acquired talent and creating equal rules

• Central governance and business-unit ownership

• Preserving a specialised capability and gaining scale benefits

• Moving quickly and allowing consultation

For each dilemma, state where the company currently leans, where it intends to lean, the conditions that may change the choice and the systems affected by it.

Review the register with the combined leadership team. Integration slows when one side thinks a choice is temporary and the other thinks it is settled.

From 200 centres to one standard

We worked with a large healthcare services organisation that had grown through acquisitions and organic expansion to more than 200 centres. Each acquired centre brought legacy practices, leadership styles and expectations. The organisation was also preparing for its next stage of growth and public-market scrutiny.

The work linked cultural articulation to daily systems. Values were built into onboarding, hiring, performance, succession and recognition. Leadership ownership was established across regions and centres. The engagement also reviewed and modernised 132 HR policies across clinical and non-clinical roles.

The organisation established a common standard where inconsistency would weaken identity, governance or people decisions. Centres retained room to operate within that standard, supported by reinforcement that did not rely only on the central team.

Walk into your next integration review and ask a different set of questions. Which important decisions still follow legacy rules? Where do employees need personal relationships to understand how work gets done? Which capability from the acquired business is at risk of being processed out of existence? Which “temporary” arrangement has no end date?

The deal may have closed. The company is created through the answers to those questions.

The Execution Readiness Assessment can help the combined leadership team find where integration intent and daily execution have separated.