Between the signing of the deal and the moment when roles, reporting lines and responsibilities are settled again, lies a period with no name. No longer the old organization, not yet the new one. For the people working during that period, this is not an abstraction. They do not know who they will report to in three months, whether their role will still exist, whether their team will remain intact. The uncertainty itself is not the problem. The problem is how long it lasts, and who accepts a different offer in that time.
The people who leave first are often not the people who perform worst. They are the people with the best alternative: those with a network, a reputation, a phone that rings. They have the luxury of not waiting for clarity. Who stays is not automatically who you would have wanted to retain — that is a lucky break, not the result of policy. This question is role-bound, not a judgment about individuals: which roles are vulnerable to departure in the first months, independent of who currently fills that role.
It is rarely a single cause. An employee who does not know whether his position will continue to exist is also the employee who does not know who the key people are in an acquisition when the two cultures do not align, and that doubt feeds itself. Uncertainty about roles leads to uncertainty about who to report to, which in turn leads to uncertainty about whether your work is still being seen. Every unanswered question makes the next question more urgent. There is no single measure that stops this; there is only closing the questions that have remained open longest, faster.
Part of the uncertainty is not a lack of information, but conflicting information. Two organizations often both have an answer to who is responsible for what, and those answers do not match. If nobody records which answer now applies, everyone keeps holding on to their own answer — until the moment it turns out to be wrong, usually in the presence of a customer or a team member. How roles stay clear across two organizations is therefore not an administrative question, but the question that determines whether people feel safe enough to stay. This becomes sharper when those two cultures do not automatically align: see how you keep roles clear across two organizations when the cultures do not align.
A specific form of uncertainty is one that does not express itself in a question, but in silence. Two people fill the same role, and neither knows for certain whether he will keep it. Both keep functioning as before, out of caution, and nobody says out loud what everyone sees. That is not meant unfairly — it is what happens when a decision is postponed. But whoever is in that position experiences it as a long-running job application without anyone using that word. What to do when two people have the same role is therefore not a theoretical question, because every week the double-filling continues is a week in which one of the two considers leaving on their own initiative.
When someone leaves during this period, it is not only a name that disappears from an organization chart. Knowledge disappears about how something works that is written down nowhere: which customer had which agreement, which system needs which exception, who maintains which relationship. That knowledge may not have been a separate line item on a balance sheet for the deal, but it was part of the value that was purchased. Preventing this from happening unnoticed starts with visibility into where that knowledge sits before someone leaves, not with an exit interview afterward — see how you prevent knowledge from leaving with someone. When two cultures structurally clash, that same question becomes more urgent and less predictable: why people leave in the unclear months when the two cultures do not align describes that situation specifically.
The generators for synergy baseline, Day 1 plan and Day 100 plan, and the integration office around them, record which roles are vulnerable, which roles are double-filled, and which dependencies arise if a key person leaves before the handover is complete. They make the decision list visible: what is being merged, what is not, and why. That is no guarantee that people will stay — no tool guarantees that — and it is no substitute for a conversation with the people themselves. It is structure that exposes earlier where uncertainty lingers longest, so that it cannot go unnoticed for three months. The tool is under construction. Those who want to work with it once it becomes available can sign up for the waiting list.
Uncertainty about roles often goes hand in hand with uncertainty about tasks: who does what, and which part of that work is actually not tied to a specific person. The work scan from FTE TO AI calculates per task which part of the work can be taken over by AI, regardless of who currently performs the task. For an organization that has just merged, that is a different entry point to the same question: not who is allowed to stay, but which work remains work — and which work no longer is.
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.