Every acquisition gets financial, legal, tax, and IT diligence. Teams of specialists comb through the numbers, the contracts, the systems. Then the people who actually have to deliver the synergy case get a town hall and a retention bonus, and leaders are surprised when the value walks out the door.
I watched this play out recently with a global logistics operator. Around 52,000 people in 27 countries, buying a founder-led regional freight business of about 3,000 employees across six Asian markets. The plan was standard: one transport management system, harmonized HR grading, centralized procurement, and a rebrand inside 18 months. The synergy case, and the gains that justified the price, rested on one assumption: that the customer-facing and operations workforce would stay and adopt the new way of working. Nobody tested that.
The synergy case rested on one assumption about people. Nobody tested it.
Why the usual fixes miss
Most teams file the people side of a deal under one word: resistance. But what actually gets in people's way comes in four distinct kinds, and each one needs the opposite response.
- Knowledge. Nobody has told them what is happening.
- Bandwidth. They know what is happening, but there is no time to do it.
- Identity. The new way threatens how they see themselves and their work.
- Loss. Something they valued is simply ending.
Training fixes the first one. Most change budgets spend the whole budget there anyway. And the window is short: between signing and close, beliefs are still forming. After that, they harden, and people leave.
What we did differently
In this deal, the team measured the people side before Day 1, instead of running the autopsy after. Every employee of the acquired business had four short conversations, personalized to their role, in their own language. We invited 3,392 people; 2,410 finished all four. The readout came back in two weeks, ahead of the second wave of integration decisions.
These were real conversations, not a survey. The AI talks with each person in their own language, listens to what they actually say, and follows up when something interesting comes out. Nobody is asked for a rating. Answers are scored one to five against examples of what each kind of friction sounds like: a 1.5 is a flashing red light, a 3.7 is fine. The lowest scores locate the blockers, and the highest scores cannot offset them. Friction is measured as shares, never names. Nothing counts as a finding until people confirm it.
What came back
Six findings came back, and two of the team's own hypotheses did not survive the data, which is exactly what a diagnostic is supposed to do.
- Managers weren't resisting. They couldn't see what the acquirer rewards. Openness scored 3.7 and learning 3.6, but incentive clarity scored 2.5. At least 58% of managers heard the same story unprompted: the colleague who challenged the system timeline at the first town hall wasn't invited to the second. People watch what happens to whoever speaks up first.
- Six markets, not one region. Indonesia and Vietnam split almost evenly between champions and skeptics. Malaysia was the readiest market outside HQ. Country-level nuance is where integration plans quietly break.
- The budget was aimed at the wrong cost. About 75% of the change spend went to training and communication. That only fixes Knowledge, which was 24% of the friction people raised. Loss was 33%, and it had no budget line at all.
- The receiving side was less ready than the acquired side. The acquirer's own finance and IT counterparts gave the lowest raw reading in the engagement, a 2.7: they doubted the change was worth it. They saw the target's practices as control failures, not practices to learn. The acquirer, it turned out, was half the problem.
- Alignment broke at the top first. The founder, the integration office, and the Group COO each gave a different answer to “What is the deal for?” And 71% of acquired managers heard “our way, on our timeline.” No message can close a gap the leaders have not decided.
- The biggest retention risk wasn't pay. Sales and customer service had the most champions (38% to 41%) and the sharpest identity risk: who owns the customer once the account moves to the Group CRM. Pay came up unprompted from just 9%.
They want the way we do it. They do not want us.
Depot lead, acquired business
Why this is a decision tool, not a report
The most-raised friction, at 66%, was simple: no stated position on roles and reporting lines after Day 1. The cost of fixing it was one decision, signed by both leaders, in six languages. Leadership interviews would not have ranked it first. They never make 2,400 people name it in their own language.
The integration office got clean inputs, not opinions. Every finding came with an owner on both sides and a first, sequenced move against the integration sequence:
- Migrate Malaysia and Singapore first.
- Freeze system migration during peak season.
- Acknowledge the sales losses before announcing any closure.
The usual diligence, and the kind nobody does
| Traditional people diligence | Behavioral diligence | |
|---|---|---|
| Coverage | Leadership interviews, a few focus groups | Every target employee, plus the acquirer's receiving side |
| Language | Mostly English | Each workforce in its own language |
| Timing | Often after Day 1 | Signed to Day 1, readout in four weeks |
| Output | Culture assessment deck | Ranked friction, decisions with owners |
| Team's hypotheses | Usually confirmed | Tested, and the wrong ones named |
Before your next deal
If you buy a company, you are buying its people's willingness to do the work. That is the real asset, and it is the one line of diligence that routinely goes unmeasured. The failure rate of M&A has been stuck at roughly 70 to 90% for decades, and the cause is consistently the human side of the deal, not the spreadsheet. You can measure the thing that actually determines the outcome. Measure it like the asset it is, with full coverage, in people's own language, and before you spend against the hypotheses, while beliefs are still forming.
This is what Pandatron Diagnose was built to do: find where integration friction actually lives, by type, across every person in scope, in time to act on it. Pick the next deal where slow adoption could quietly cost you the synergy case. Name it, and run the diligence nobody does, before Day 1.