Two cultures that are far apart do not clash immediately on the work floor. They first clash in the minds of the people who see exactly how big the difference is. These are often not the people at the top of the org chart. They are the people who know why a process is the way it is, which customer needs which exception, which supplier only works with one specific colleague. That knowledge is written down nowhere. It sits in people, and people who do not recognize themselves in the new culture leave sooner than planned.
There is a temptation to treat cultural difference as something that will resolve itself later, once the structures are in place. That is exactly the assumption that lets knowledge slip away. While the organizational structure is being fixed, those who find the new culture unfamiliar remain without insight into what is expected of them. They fill in that uncertainty themselves, and not always to the benefit of the merger. You can read more about how that period exactly works in why do people leave in the unclear months.
Before you can steer toward retention, it must be clear who the key people are — not as an honorary title, but as a role description: who has knowledge, relationships or authorities that exist nowhere else. That overview should exist independently of the question of whether someone "culturally fits". It is an inventory of what the organization depends on, not an assessment of individuals. How you build that overview is described in who are your key people in an acquisition.
Cultural difference becomes sharper in the places where two organizations have the same function twice. Two financial directors, two heads of operations, two people who "know the customer". If it does not quickly become clear how those two roles relate to each other, a competition arises to remain relevant — and that competition often runs along cultural lines, not along quality. Whoever feels excluded leaves with the knowledge that no one else had. An approach for that situation is described in what do you do when two people have the same role.
Even without duplicate functions, unclarity about who decides on what is a driver of departure. In a culture that already feels unfamiliar, an unclear role is doubly unsettling. People who do not know what is expected of them within the new structure sometimes seek that clarity outside the organization. How roles remain legible while two organizations exist side by side is described in how do you keep roles clear across two organizations.
The question of whether two cultures should be brought together is not a side issue — it is a question that recurs with every integration decision. Sometimes the answer is that merging on a particular part costs more than it delivers, precisely because it is the people who carry the value. That consideration should be raised structurally, not as an afterthought exception. When that is the case, you can read in when does integrating destroy value, and what you can deliberately keep separate is described in what do you deliberately keep separate.
The generators for synergy baseline, Day 1 plan and Day 100 plan bring these questions together at the moment they belong: who carries knowledge, which roles overlap, what remains deliberately separated. The integration office keeps track of which dependencies exist between people and processes, and which decisions are on the list to integrate or not. This is not advice about who should stay or leave — that remains up to you. It is structure that prevents the question from only being asked at the moment someone has already left.
This tooling structures the questions and records the dependencies. It does not show experience with previous integrations, because we are not building that track record here. There is no guarantee that knowledge is retained, not even with the best overview. What it does do is prevent cultural difference from going unnoticed until it is too late to do anything about it.
If knowledge is the risk, the follow-up question is what happens to the work itself once two organizations organize it differently. That is not only a question about people, but also about tasks: which part of the work that currently rests with a key person is actually task work that can be redistributed or automated. The work scan of FTE TO AI calculates per task which part of it can be taken over by AI, thereby providing a picture of where the dependency on one person is greatest — and where it can be reduced with less risk.
The generators and the integration office are now being built. Anyone who wants to make use of this as soon as it becomes available can sign up for the waiting list.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.