The human capital value gap is the distance between what the deal model assumes people and capability will deliver and what the combined organisation can execute. A transaction can have sound financial logic and still miss its value case because key knowledge, trust or decision speed was not modelled.
I treat the gap as a question the deal model has to answer in plain language. Which revenue or cost assumption depends on a person, a relationship or a decision? Where does that capability sit today? What could interrupt it after close? If the model cannot answer, the gap is real, even if nobody has yet put a number on it.
Where the human capital value gap opens
WTW’s 2026 M&A research highlights the importance of identifying key talent below the executive level and the difficulty of culture alignment. That points to a layer a deal model can easily leave undescribed: the people between the executive team and the work, who hold customer context, technical judgement and local decision-making.
The value gap becomes visible when a deal model names revenue synergies but cannot name the people, relationships or decisions that must produce them. I translate the gain into a capability statement, then ask where that capability currently lives and what could interrupt it after close.
A critical role is not always a senior role. The person who knows how a customer makes a difficult decision, how a system behaves at its edge or how a team resolves conflict may sit well below the executive level. Losing that context can delay value even when the org chart looks complete.
A deal model is built from what can be counted, and the capability behind a gain is rarely countable. That is not a reason to leave it out. It is a reason to describe it in words, name its owner and decide how it will be checked.
Three steps that close the human capital value gap
I bridge the gap in three steps: name the capability the deal depends on, locate where it currently lives and design how it will move into the combined business.
- Value case: Name the capability the deal depends on.
- Dependency: Locate the relationships, judgement and context behind it.
- Transfer: Give the combined business a way to reproduce the capability.
Step one: Name the capability
The first step changes the conversation from “retain talent” to “protect the capability that creates the value.” A retention payment answers the first question. It does not tell the board whether anyone else can make the same judgement call.
Take a hypothetical example. A deal case that rests on selling more to the acquired customer base is really a case about who owns those customer relationships and whether the two sales teams will introduce one another. Writing that sentence into the model turns a revenue line into a capability statement that someone can own and test.
Step two: Locate the dependency
The second step examines dependency. If a customer relationship, process or technical judgement lives with one person, retention alone does not create transfer.
The diligence conversation should include the people who perform the work, not only the owners of the spreadsheet. Ask where a decision depends on one person, where a process is informal and where a relationship would be difficult to transfer. Those details change the risk picture before the purchase agreement is signed.
A capability can be valuable without being documented. That is a reason to capture it, not a reason to discount it. Pair the specialist with someone who can learn the work, record the decision rules and test them in an ordinary week.
Step three: Design the transfer
The third step designs an operating rhythm that lets the capability travel while integrating a company without losing acquired capability. That may mean paired leadership, decision logs or a deliberate handover.
BCG’s full-potential PMI work reinforces the value of combining integration with transformation rather than treating the deal as a cost programme. Transformation can close the gap when it strengthens the capability the deal depends on. That may mean changing decision rights, simplifying a handoff or giving a newly combined team a shared customer outcome.
Each mechanism does a different job. Paired leadership puts a second person inside the decision until they can make it unaided. A decision log records the reasoning behind choices that used to live in one head. A deliberate handover sets a date, an owner and a test of whether the work continued. I would choose among them according to how much of the capability is judgement, how much is relationship and how much is process.
The human-capital ledger the board should see
Boards should see a human-capital value ledger alongside the financial plan: critical roles, capability dependencies, trust signals and integration milestones. The ledger should show dependencies, transfer actions and leading signals. Examples include paired customer ownership, documented exceptions, cross-training and evidence that a second leader can make the same call under pressure.
The board needs a clear view of the gap between reported assets and usable capability. Put the risk beside the action, the owner and the date for evidence. If the evidence does not arrive, change the integration plan rather than explaining the delay away.
- Look below the executive layer for the people who hold the customer, process or technical context the deal depends on.
- Track transfer actions alongside retention actions; keeping a person is not the same as making their judgement reproducible.
- Translate each revenue gain into the capability that must produce it, and name an owner for that capability.
- Connect trust signals to integration speed by recording where bad news travels slowly or decisions return to one person.
- Show the board where human capability is becoming reproducible through owners, evidence and a tested handover.
A ledger earns its place only if somebody maintains it. Give it an owner in the integration office, review it in the same meeting that reviews financial milestones and let an entry stay open until the evidence says otherwise. An entry that quietly disappears is more worrying than one that stays red.
The board can see the gap closing when human capability is treated as an owned asset with evidence, not as a soft risk described only in narrative.
Why culture alignment belongs in the value case
Culture alignment belongs in the value case because trust changes speed. If people do not know which commitments survive the deal, they protect themselves, delay decisions and keep knowledge local. Those behaviours become integration cost.
This is where the talent work and the culture work meet. A specialist who is willing to share what they know will do so only if they believe the knowledge will be respected after close. A manager who expects the deal to remove their authority will keep decisions close. Both behaviours are rational, and both are visible before close if someone is looking.
A practical test is to ask people on both sides what they expect to happen to their role in the first year. Where the two sets of answers differ, trust is thin, and the speed assumptions in the model may be more optimistic than the organisation can deliver.
A lesson from The Leadership Shift
In The Leadership Shift, I write about a global financial organisation with cultural division, lost intellectual property and repeated failed transitions. The value at risk was human as much as financial. The integration work had to restore shared purpose and leadership behaviour before the organisation could reliably transfer knowledge. That is the human-capital gap I look for in a deal model.
Questions to ask before the purchase agreement is signed
A human-capital value gap becomes visible when a transaction asks what the business can keep doing after the deal. Start with the roles that carry customer trust, technical judgement or regulatory knowledge. Name the evidence that shows those capabilities are real, then decide which ones the integration plan must protect.
Before close, I would test which capability the deal depends on and who owns its transfer into the combined business.
Put the question to the CHRO, the integration lead and the commercial owner of the deal together, because each will describe a different part of the dependency. The commercial owner knows which customer outcome the model needs. The integration lead knows which teams will merge first. The CHRO knows which roles are exposed. The answer only makes sense when the three accounts are laid side by side.
When the evidence is thin, the legitimate responses are to slow a consolidation, extend a handover or accept that a capability the deal was meant to buy will have to be rebuilt. Each is better chosen early and openly than discovered after the first results meeting.
The measure of human-capital value is practical: can the combined organisation make the important decisions, serve its customers and keep its knowledge when the people at the centre change roles?
To make these questions part of your own deal process, I would begin with the Leadership Capability Architecture framework, which gives the board and the integration leads a shared view of decision rights, routines and capability. CapabilityAI, my AI leadership coach, is based on the same view of decision rights, routines and capability, and the organisational change and capability pathway describes how the same questions are worked through with leadership teams.
Further reading: The Staffing Batting Average: A Process for People Decisions