The due diligence for a significant acquisition covers a great deal. Financial statements, contracts, intellectual property, regulatory compliance, customer concentrations, technology stacks. The best processes also cover culture: interviews, engagement surveys, values assessments, the judgement of senior leaders who have spent time in both organisations.
What almost none of them cover is what the two organisations actually understand. Not their values, not their cultural archetype, but the specific collective knowledge they hold about the market they are entering together, the customers they will serve, the operational reality they will have to manage, and the strategic assumptions each brings to the combination. This is the understanding gap. It is where most integrations fail.
Why cultural due diligence misses it
Culture assessments identify patterns: how decisions tend to be made, how conflict is managed, how hierarchy operates, how innovation is rewarded or discouraged. They are useful. They are not the same as understanding what the organisation thinks.
The understanding problem is more specific. It is about the models of the world that each organisation is operating on, the knowledge that is so embedded in daily practice that nobody has made it explicit, and the assumptions about how things work that will only become visible when they collide with a different set of assumptions in the merged entity.
The integration failure cases are almost always, in retrospect, a story about two different models of the world that were never surfaced and examined before they were combined. The assumptions and thinking behind strategy choices or innovation or transformation programs were never stated because inside each organisation they were simply obvious. It only becomes a problem when the two sets of obvious assumptions meet and find they are incompatible.
What the two organisations understand about the business they are entering together is the most important thing you do not know before you sign.
What standard integration planning cannot surface
Integration workstreams cover technology, people, customers, processes. They are planned on assumptions about what the combined entity will look like, how decisions will be made, which systems will be primary, which processes will be standardised.
Those assumptions are built from the model that the acquiring organisation holds of the target, and vice versa. They are rarely built from a genuine examination of what the target organisation understands about itself and its business. The knowledge that lives in the organisation, distributed across functions, levels and tenure, is not in the data room.
The result is integration plans built on incomplete pictures. They encounter resistance that was not anticipated. They discover operational realities that should have been visible. They combine two strategies that were coherent separately and incoherent together. The problems emerge six months in, under the pressure of post-merger performance expectations, when the cost of course-correction is high.
What genuine understanding due diligence looks like
The organisations that manage complex integrations well, that actually realise the value of the combination, have almost always done something before close that most do not: they have found a way to understand what the target organisation actually thinks about the business it is in, the customers it serves, what next, and the assumptions the combination is being built on.
This is not a survey. It is not a series of leadership interviews that produce a synthesis. It is a structured process in which the distributed knowledge of the target organisation, and that of the combination, across functions, levels and tenures, is assembled in a form that makes its structure visible. Where are the assumptions? Where do they come from? Where do they differ from the acquiring organisation's model? Where is the knowledge that is not in any document but that the combined entity will need?
Hunome creates this picture. Before close, or as early in the integration as access allows, a deliberation is opened to participants from both organisations on the strategic, operational, and cultural questions that the integration will have to resolve. The Hunome product enables mapping contributions as they come in: identifying where assumptions clash, where knowledge is concentrated, where the two organisations hold genuinely different but compatible models that need to be surfaced before they collide.
Leadership does not receive a culture report. They receive a map of the shared and divergent understanding of the combined entity: the understanding gaps that will become integration failures if they are not addressed, and the shared understanding that is already there to build on.
The assumptions that cause integration failures are almost never hidden. They are simply so embedded in each organisation's normal that nobody thought to examine them before combining.
The timing
This work has to happen before the plan is set. Integration plans that are built on an incomplete picture of what the two organisations understand are expensive to revise. The discovery that comes six months in is not cheaper for arriving later. By then the cultural collision is already causing turnover, the operational assumption is already causing customer impact, and the strategic incompatibility is already visible in the numbers.
The understanding gap is bridgeable. It is significantly cheaper to bridge if started before the integration begins.