Protect What You Paid For

After an acquisition, one of the first sensible questions is often: Who are the people we cannot afford to lose? The question matters, but it can also mislead. It encourages us to turn organisational capability into a list of names, usually senior leaders, high performers and obvious technical experts. Retention packages follow. Calls are made. People are reassured. Yet some of the most consequential losses after an acquisition are not caused by the departure of the people whose names appeared on the original list. They occur when the organisation loses somebody who connected work, carried tacit knowledge, held a customer's confidence or knew how to recover the system when the formal process stopped working.

The deeper problem is that key-person risk is not simply the risk of losing people. It is the risk of losing capabilities, relationships and memory that happen to depend upon them. That distinction changes the task. The aim is not to preserve an acquired organisation in amber, nor to create a privileged class of indispensable employees. It is to understand where value is unusually concentrated, protect it through the vulnerable transition, and then make the organisation stronger by spreading knowledge, building substitutes and creating new connections.

Critical does not mean senior

Hierarchy is a poor proxy for organisational importance. Senior leaders can be genuinely critical, but so can the operations coordinator who knows which three people must be involved before a difficult job is accepted, the engineer customers ask for by name, the administrator who understands the exceptions in a supposedly automated process, or the account manager who can tell from a two-line email that a long-standing customer is quietly becoming dissatisfied. These people may have little formal authority while exercising considerable practical influence.

This is one reason organisational charts are an incomplete guide to acquisition risk. They describe formal accountability, not necessarily how expertise, trust and information move. Research on workplace networks similarly shows that informal connections matter. A large longitudinal study of communications during a corporate merger found that employees who developed more cross-legacy connections were less likely to leave, illustrating that post-merger retention and integration are partly network phenomena rather than simply individual employment decisions.

That does not mean every well-connected employee is critical or that network centrality should become another crude score. Informal networks can also reproduce poor practice, hoard information and bypass appropriate governance. The practical point is narrower: if diligence only asks who holds the senior roles, it can miss people through whom disproportionate amounts of useful work travel.

Knowledge is not the same as documentation

Acquirers often respond to key-person dependency by asking for documentation. That is sensible. If an important process exists only in one person's head, writing down what can be written down is an obvious improvement. But documentation solves only part of the problem because knowledge is not homogeneous. Some knowledge can be codified relatively easily. Other knowledge is tacit, contextual and learned through repeated exposure to situations in which the rules do not quite provide the answer.

Research on organisational routines and transactive memory helps explain why. Organisations remember partly through procedures and routines, but also through a distributed understanding of who knows what. A capable team does not require every member to know everything. It needs people to know enough about the expertise around them to retrieve the right knowledge when it is needed. That shared cognitive map can be damaged when experienced people leave, teams are reorganised or familiar relationships are broken faster than new ones are formed.

The implication is important for integration. A folder full of process documents may preserve instructions while losing the network that knew when those instructions applied, when they did not and who should be consulted when circumstances became unusual. Conversely, relying on experienced employees without documenting or transferring what they know preserves capability only temporarily. The useful objective is therefore neither documentation nor retention alone. It is knowledge continuity.

Acquisitions should enable knowledge to move both ways

There is a further trap here. The acquiring organisation can assume that knowledge transfer means teaching the acquired company how the larger group works. Sometimes that is exactly what is needed. The buyer may possess stronger controls, better technology, deeper management capability or more mature processes. Yet acquisitions are also undertaken precisely because the target possesses something the acquirer wants: expertise, customers, technology, intellectual property, market access or ways of working that cannot simply be recreated internally.

Empirical research on UK cross-border acquisitions has examined knowledge transfer in both directions and found that functional integration and shared goals can facilitate bilateral knowledge flows. This matters conceptually. Integration should not be imagined as knowledge travelling downhill from owner to acquired company. The strategic opportunity is to make useful knowledge mobile in both directions and to combine resources that previously sat in separate organisations.

That requires humility from the acquirer and openness from the acquired organisation. Neither is automatic. The buyer may mistake ownership for superior competence. The acquired team may romanticise its existing practices and resist useful discipline. The relevant question is not whose knowledge wins. It is which knowledge should travel, what must remain context-specific, and how the combined organisation becomes better at using both.

Protect relationships, not just employees

Some of the value at risk after acquisition sits outside the employment relationship altogether. A customer's confidence may depend on a particular account manager, but also on the operations team behind that person. A supplier may repeatedly rescue difficult situations because of years of reciprocal trust. A regulator may know which specialist inside the business can explain an unusual issue quickly. An external partner may tolerate occasional inconvenience because previous experience has demonstrated that the organisation will ultimately deliver.

These relationships are easy to damage accidentally because integration often changes several parts of them at once. A new account owner is appointed, the product name changes, invoicing moves to another system and the familiar operational contact loses authority. Each change may be defensible. From the customer's perspective, however, the organisation they trusted may appear to have disappeared.

Protection therefore needs to ask more than who should receive a retention bonus. It should ask: Which relationships help this business create value, what makes those relationships work, and how dependent are they on particular people, names, routines or promises?

Retention bonuses buy time, not capability

There are circumstances in which financial retention incentives are entirely rational. Acquisition creates uncertainty precisely when competitors and recruiters may see an opportunity. If somebody holds scarce knowledge required for a critical transition, paying them to remain through that transition may protect considerable value. But a retention payment is best understood as buying time. It does not, by itself, transfer knowledge, rebuild a network or make the organisation less dependent on the person being retained.

This creates an awkward possibility. An acquirer can successfully retain all its named critical people for twelve or eighteen months and still emerge with essentially the same fragility it bought. When the retention period ends, the organisation discovers that nobody else has learned the role, customer relationships remain concentrated, decision authority is still unclear and important knowledge is still retrieved by asking the same individual.

That is not capability protection. It is dependency on a timer.

Protect the capability by making it less fragile

A better approach is to treat every material key-person dependency as a development problem. If one person knows something genuinely important, who else should learn it? If a customer relationship depends heavily on one account manager, who else should become credible to that customer? If a specialist makes difficult decisions using years of experience, can less experienced colleagues observe those decisions and understand the cues being used? If an operational recovery depends on one coordinator's network, can the relevant contacts and escalation routes become part of a wider team capability?

This is where training and development become part of the investment thesis rather than an employee benefit sitting somewhere in the HR budget. Shadowing, paired work, deliberate handovers, scenario practice, communities of expertise, after-action reviews and carefully designed succession can convert individual experience into organisational capability. Technology and AI may increasingly help by making prior cases, decisions and expertise easier to retrieve, but only if the organisation captures useful context rather than filling a repository with documents nobody trusts.

The objective is not to make expertise irrelevant. Strong organisations need experts. The objective is to stop expertise becoming a single point of organisational failure.

A simple Capability Protection Map

For the first year after acquisition, I would make the protection problem explicit. For each capability materially connected to the investment thesis, identify the outcome it enables, the people and relationships on which it currently depends, where the relevant knowledge resides, what would happen if one or more dependencies disappeared, and what is being done to strengthen continuity.

This produces a different conversation from a conventional key-talent list. A person may be important because of technical expertise, customer trust, organisational memory, network position, decision authority or several of these at once. A brand or product name may matter because it acts as a trust signal. A routine may look inefficient yet contain an important adaptation to customer need. A supplier relationship may be carrying resilience that has never been priced explicitly.

The map should also contain an exit condition. What would need to become true for this dependency no longer to worry us? Perhaps two other people can now perform the task. Perhaps the process has been simplified. Perhaps the customer knows a wider team. Perhaps the expert's judgement has been turned into scenarios used in training. Perhaps the dependency was investigated and proved less important than everybody assumed.

That last possibility matters. Capability mapping should challenge folklore as well as reveal risk. Organisations frequently describe people as indispensable when what they really mean is that nobody has tested the assumption.

Do not protect yesterday at the expense of tomorrow

There is a final tension. The language of protection can become too conservative. An acquisition that spends all its energy preserving existing relationships, identities and routines may fail to create the new capabilities that justified the transaction. Some people should move into different roles. Some expertise should be combined. Some product identities should disappear. Some local workarounds should be replaced by stronger systems. Some employees who were influential in the old organisation may be less central in the new one.

The purpose of protection is therefore not permanence. It is to prevent valuable capability being destroyed before the combined organisation understands what it is doing. Once that understanding improves, the ambition should become developmental. Protect what is fragile enough to lose, transfer what should become organisational, combine what becomes more valuable together, and deliberately retire what no longer serves the future.

This is a more demanding interpretation of key-person risk. It asks investors and leaders to see people not as human assets that can somehow be owned, but as participants in a system through which knowledge, trust and judgement become economic value.

Protect what you paid for, certainly. But the strongest form of protection is to build an organisation that no longer needs that value to remain trapped in one person.