Integrating a company without losing the capability you acquired starts with a different question from the usual reporting-line debate. What did the deal buy, and which conditions allow that capability to keep producing value? The answer may include customer trust, specialist judgement, a relationship network, a data convention or a way of resolving exceptions. Name those conditions before changing the structure, then make the transfer and the protection of that capability part of the integration plan.
Why acquired capability disappears after a deal
Integration teams are often asked to create one operating model quickly. That pressure is understandable, but speed can turn difference into a defect before leaders understand what the difference is doing. A specialist team may look inefficient beside the buyer until someone traces the customer decisions it makes, the information it holds and the risks it absorbs. If those conditions are removed, the team can remain in the organisation while the capability has already gone.
The first warning sign is a plan that treats people as interchangeable holders of process. Documentation matters, but a process note rarely explains why an exception was handled a certain way, which relationship made a decision possible or when a local judgement protected a customer. The integration question is therefore not whether a practice looks different. It is whether the difference is carrying value, risk control or context that the combined business still needs.
Map the capability before changing structure
I map capability before structure. Start with the work that creates value, then trace the decisions, relationships, information and routines that make the work possible. Include the people who receive the output, the people who make the judgement and the people who carry the consequence when the judgement is wrong. This is more useful than copying the organisation chart because it shows where the capability actually lives.
- Customer promises and decisions that depend on the acquired team
- Specialist knowledge that is not visible in a process document
- Data, systems and permissions required to act without delay
- Relationships with customers, suppliers, regulators or internal partners
- Routines that reveal problems early and create a reliable hand-off
A map should lead to a decision, not become another integration artefact. For each capability, name what must be protected, what must be transferred and what can be standardised. Give the decision an owner and a review date. If the team cannot explain why a condition matters, test the assumption with a live customer decision or an operating incident before changing it.
| Capability condition | Protection decision | Evidence to review |
|---|---|---|
| Customer relationship | Keep the relationship owner involved during the interim model | Customer continuity, escalation quality and decision speed |
| Specialist judgement | Pair the expert with the receiving role on live work | Quality of exceptions and confidence of the new owner |
| Data convention | Document the rule and the boundary for changing it | Error rate, audit trail and time to resolve an exception |
| Operating routine | Retain it until the combined process is tested | Handover quality and effort required from managers |
Transfer judgement, not just documents
The transfer map needs a social route as well as a written one. Pair a person from the acquired team with the person who will carry the work after integration. Let them solve a live problem together, then review the decision. The receiving colleague learns the judgement behind the method, while the original expert sees which context has changed. That exchange is the part a document cannot provide.
Use shadowing, paired decisions, recorded examples and short reviews. Do not ask the acquired expert to create a perfect manual before anyone else performs the work. The test is whether another capable person can make a sound decision with the right information, know when to escalate and explain the reason for the choice. Transfer is visible when the work becomes less dependent on one person without becoming less reliable.
- Choose one live decision: Select a customer, operating or people decision that depends on the acquired capability.
- Pair the roles: Put the original expert and the receiving owner together on the real work, not a classroom example.
- Review the judgement: Compare the decision with the intended outcome and record what context was needed.
- Move ownership gradually: Let the receiving owner lead while the original expert challenges the reasoning and remains available.
- Test independence: Review the next comparable decision without the original owner in the room.
Use an interim operating model as a protection mechanism
An interim operating model is not a sign that leaders have failed to decide. It is a way to preserve a productive pattern while the combined organisation learns where standardisation will help. McKinsey’s M&A operating-model research makes the same distinction between a day-one model and a later end state. The interim model should state what changes now, what remains protected, who decides exceptions and when the evidence will be reviewed.
The model also needs a boundary around local practice. Protect the routine that keeps a customer promise or a specialist capability alive, but give it an owner and a reason. Do not leave the exception as informal goodwill. If the combined business later changes the routine, people should be able to see what problem the change solves and what evidence made the decision reasonable.
- Protect: Keep the conditions that make the acquired capability effective while the combined model is being tested.
- Transfer: Move judgement and context through paired work, observation and deliberate review.
- Integrate: Standardise when the combined business understands the source of value and can reproduce it.
Protect the people who carry context
Retention risk is often reduced to a list of names. A better question is which customers, decisions, systems or routines would be hard to reproduce if a person left. That dependency view gives leaders something to transfer and protect. It also makes a retention conversation more honest because the person can see which knowledge the organisation values and which support will remain during the transition.
The acquired team needs a credible answer to what will remain distinctive. If every difference is labelled temporary, people assume the buyer has already decided to erase the source of value. State what is protected, what is being tested and what is undecided. Then give people a route to raise a concern when a new process loses important knowledge. Review the concern and tell the team what happened.
In The Leadership Shift, I describe a merger where the operational transition had already been attempted twice. The lesson was not that people resisted change. It was that the operating conditions that let their judgement work had not travelled with the structure. That is the leadership responsibility in an integration: make the conditions visible, then decide which ones the new organisation must carry forward.
A practical first 90 days
The first 90 days should include a few shared decisions rather than a long list of harmonisation tasks. Choose one customer issue, one operating control and one people decision. Let both teams show their reasoning, then record the rule that will apply next time. The record is more valuable than a slogan about integration because it can be tested by a manager who was not in the deal room.
Keep a short list of decisions that remain open. Each line needs a person, a date and the evidence needed to close it. When a local practice is retained, say what it protects. When it is changed, say what problem the change solves. This prevents unresolved questions from disappearing into a general workstream and gives the leadership team a place to challenge assumptions without reopening the whole transaction.
People who join after completion should be able to understand the arrangement without the original deal documents. Put the decision rules, protected capability and review dates in a short operating note. Use a real example from the first months to explain where the rule helped and where it needed changing. Good integration becomes a living set of choices, and living choices need an owner.
Measure whether capability has actually moved
The measure I would watch is not uniformity. It is the quality and speed of decisions at the boundary between the two businesses. If people know who decides, where knowledge sits and when an exception will be reviewed, the integration is doing useful work. If routine decisions keep returning to the deal team, the new structure has not carried enough judgement into the operating system.
Review the capability after the first operating cycle, not only at the formal close. Ask whether customers still receive the same value, whether the receiving team can make the decisions it used to make and whether the new structure has created unnecessary approvals. A small correction early is more respectful of the acquired capability than a late rescue after the strongest people have already left.
The strongest integrations preserve capability deliberately rather than sentimentally. If a routine no longer serves the combined business, change it and explain why. If a relationship or practice is still creating value, protect it while the wider model settles. The judgement becomes easier when leaders have named the capability, the evidence and the conditions that matter.
| Signal | What it tells you | Next decision |
|---|---|---|
| Customer continuity | The acquired promise is still understood | Protect the relationship or repair the hand-off |
| Decision quality | Judgement is travelling with the work | Extend paired practice or clarify authority |
| Escalation pattern | The new model is creating friction | Remove an approval or strengthen a control |
| Manager confidence | The operating note is usable | Rewrite the rule or give managers a real example |
What to do next
Start with one capability that the deal was meant to add. Map its conditions, name the person accountable for protecting them and choose one live decision for the transfer test. Then set the review date before changing the reporting lines. Leaders who want a broader view can compare this approach with building leadership capability at scale, measuring capability across an organisation and leading organisational transformation.
The integration plan should say how learning will be heard. Give acquired specialists a route to flag a loss of capability, give the integration owner authority to respond and review the evidence with the leaders who depend on the work. That is how the combined business protects what it bought while still becoming something new.
The final test is simple: can the combined organisation make the important decisions without the original team carrying every piece of context? If yes, capability has moved. If not, change the conditions before declaring the integration complete.