Why Culture Due Diligence Should Start Before the Deal Closes

Culture due diligence belongs before the deal closes, because that is the last point at which the buyer can still change the design of the deal. It is not a values workshop. It is an investigation into how work and power move: who decides, who is heard, what gets rewarded and where the real capability sits. Before close, I look for evidence in decisions, incentives, meetings, talent movement and the stories people tell about speaking up.

I would expect a deal team to test the financial model, the contracts and the systems thoroughly. The people side deserves the same discipline, and it deserves it while the price, the structure and the integration plan can still respond to what is found.

Why culture due diligence has to start before close

HBR’s M&A guidance emphasises the integration experience of acquired employees. That experience starts before the legal close, when uncertainty is already shaping behaviour. WTW identifies culture alignment and key talent below executive level as major human-capital concerns in transactions. The risk sits deeper than the leadership team.

Between signing and close, people in the target organisation do not wait for an integration plan to decide what the deal means for them. They watch who is consulted, which meetings quietly disappear and how leaders answer a direct question. Those reactions are evidence for the buyer as well. They show how the organisation behaves when it is uncertain, which is the condition the whole integration will run under.

That is why I treat timing as part of the method. A finding made before close can change the price, the deal structure, the retention plan or the order in which teams are brought together. The same finding made afterwards can often only change how people are told.

What culture due diligence should reveal

The evidence map asks five questions: who decides, how conflict is handled, what gets rewarded, which leaders are trusted and where capability depends on one person. None of them needs a survey. Each can be tested in a meeting, a decision record or a conversation with the people who do the work.

1. Who decides: Find who can approve, stop or reverse a material choice, and compare the answer with the organisation chart.
2. How conflict is handled: Watch whether disagreement is raised in the meeting or after it, and whether it ends in a decision or a delay.
3. What gets rewarded: Look at who was promoted, who was protected and which behaviours were quietly tolerated.
4. Which leaders are trusted: Ask where bad news is taken first. That is usually where the trust sits, and it is not always the most senior name.
5. Where capability depends on one person: Note every customer relationship, process or judgement that lives with an individual rather than a team.

The buyer should record cultural strengths worth preserving, not just risks to remove. Integration destroys value when it treats difference as inefficiency. A diligence file that lists only problems teaches the integration team to look for things to fix, which is a poor way to meet the people whose goodwill the deal needs.

Test the story against behaviour

Culture due diligence asks how work really moves before the deal makes the answer expensive. I look at who can stop a decision, which leaders are trusted with bad news and where a customer commitment depends on informal knowledge. Those clues are usually available before a formal integration plan exists.

The buyer should interview for contradictions, and I compare the formal operating model with the lived one. If the policy says decisions are delegated but every material choice returns to the founder, that is a dependency. If the company celebrates speed but punishes a failed experiment, that is a learning constraint.

A contradiction is not a verdict. It is a question to take back to the people involved: what happens when the founder is away, what happened the last time an experiment failed and who learned from it. The answers separate a stated value from a working one.

Where a deal can hide dependency

Dependency hides in ordinary places. A customer commitment may rest on one person’s informal knowledge. A reporting line may be shorter on paper than it is in practice. A specialist below the executive layer may be the only person who knows how a system behaves at its edge. None of this appears in a data room, because none of it was written down for a reader outside the business.

I would ask the diligence team to turn each row of that table into a short note: the evidence found, who supplied it and what it implies for the first 100 days. A row with no evidence is still a finding. It tells the buyer where the deal is relying on assumption.

Run the investigation so people tell the truth

The acquired organisation also needs to see that the investigation is reciprocal. The buyer should explain what it is trying to learn and share which strengths it intends to protect. That reduces the defensive behaviour that makes culture evidence unreliable.

That openness has a practical edge. People who believe the exercise is a search for redundancies give careful, defensive answers, and the buyer ends up reading a performance rather than evidence. People who can see that the buyer is also trying to protect something are more likely to describe how work really happens.

I also look for evidence that trust will travel across the two organisations. Watch how leaders handle a missed promise, an awkward escalation and a disagreement about authority. Those moments carry more information than a statement drafted for the announcement.

Record hypotheses, not scores

The output is a set of hypotheses to test with employees, not a culture score that pretends to be precise. I record hypotheses, not scores. A statement such as “decisions move through trusted specialists” can be tested with examples, customer evidence and observation. A single culture number hides the very variation leaders need to understand.

Each hypothesis needs an owner and a way of being proved wrong. If decisions do move through trusted specialists, the next customer escalation should show it. If it does not, the hypothesis changes and the integration plan changes with it.

The diligence question I would insist on

Before close, I would test which cultural dependency the deal cannot afford to lose and who owns its transfer. A deal that cannot name that dependency has not finished its diligence. A deal that names it without an owner has only moved the risk to the integration team.

Take one decision the transaction will force, such as who keeps the customer relationship that carries the revenue case. Ask the CEO, the board, the HR lead and the deal team what evidence each needs before agreeing, and write down what would change their minds. The exercise is useful when the answer alters the integration plan, not when it confirms it.

Protecting strengths without freezing them

A sound deal protects the behaviours that create value without assuming every existing habit deserves to survive unchanged.

Protection needs a reason, a boundary and a review date. Name the practice, say why it works and set the conditions under which it can change. Without those three, a protected habit becomes a permanent exception and the combined organisation inherits two ways of doing everything.

Questions for the first 100 days

A pre-close evidence map is useful only if it changes the first 100 days. The integration plan should identify conversations that cannot wait, talent dependencies that need protection and operating differences that should be tested rather than standardised immediately.

• Test how bad news travels before the deal closes. Give someone responsibility for the observation and record what happens in a real meeting or escalation. A useful finding changes a decision; it does not sit in a culture slide deck.
• Compare formal delegation with the decisions people actually make, especially when a customer or integration choice carries risk.
• Explain the purpose of interviews to acquired employees so the evidence reflects trust rather than defensive performance.
• Convert culture hypotheses into first-100-day actions with an owner, an observation and a review point.
• Protect strengths without pretending the organisations are identical; preserve what creates value and test what creates drag.

In the first live decision where the two organisations must rely on one another, I watch who speaks, what evidence is trusted and where the handoff stalls. Someone outside the diligence team should challenge what I conclude, because the people who gathered the evidence are the least likely to see its gaps.

The observations then belong in the integration review, where they can change something. Treat an exception as a test of the original hypothesis and give a named person the authority to act on it, so the combined organisation can repeat the behaviour after the deal team has moved on.

A lesson from The Leadership Shift

One field story in The Leadership Shift involves a large financial organisation where business units were divided, employee motivation had dropped and compliance risk was rising. Several transition attempts had failed because priorities were not shared. Culture due diligence should look for those operating signals before close, when the cost of correcting a mistaken assumption is still manageable.

What the first month teaches people

The first month after close is where diligence either pays or is wasted. People learn what the new organisation values from its first decisions, and they compare those decisions with what the diligence team asked them.

Bring the acquired team into the design of the first operating changes. They can show which practices protect customers, where local knowledge is held and which rule would create unnecessary delay. Listening does not mean keeping every practice. It means changing the right one for the right reason.

The integration lead should keep a short record of the choices made in the first month. Write the decision, the evidence and the owner. Review the record with both sides of the business so a workaround does not become an invisible standard.

A culture risk needs an action that people can see. It might be a shared decision forum, a protected specialist role or a change to how exceptions are reported. Name the action and return to it when the work is busy.

The deal is becoming one organisation when people can explain how decisions are made, where knowledge sits and how a concern will be heard. That is the culture evidence worth carrying into the next integration review.

To turn this into a working diagnostic for a live deal, I would start with the Leadership Capability Architecture framework, which gives the deal team a shared map of decision rights and routines. CapabilityAI, my AI leadership coach, is built from the same framework, and the organisational change and capability pathway shows how the same questions are worked through with a combined leadership team.

Related Reading

• How Do You Build One Culture After a Merger Without Erasing Both?

Further reading: Culture as a Competitive Weapon

Further reading: Maintaining Motivation in a Hybrid Workplace