Post-merger integrations have a predictable shape. The first ninety days are energetic and focused. There is a clear mandate, a dedicated team, and enough senior attention to keep things moving. Around month four, something shifts. The integration team starts to wind down. The workstreams are declared complete. And then, quietly, the organisation discovers that the integration has not actually happened.
Mistake one: declaring workstreams complete before the behaviour has changed ¶
An integration workstream is not complete when the new org chart is drawn or the new process is documented. It is complete when the people in the organisation are actually behaving differently. The gap between documentation and behaviour is where most integration value is lost. A structured check-in at the twelve-week mark, asking whether the new behaviour is actually happening, is the most reliable way to catch this before the integration team disperses.
Mistake two: releasing the programme manager too early ¶
The integration programme manager is the person who knows where all the dependencies are, which workstreams are genuinely complete and which are complete on paper, and which relationships between the two organisations are still fragile. Releasing this person back to their line role at month four, just as the hardest part of the work is beginning, is one of the most common and most expensive integration mistakes. The programme manager should stay until the integration is actually done, not until the project plan says it is done.
Mistake three: underestimating the informal integration ¶
The formal integration, the org chart, the reporting lines, the systems, is the part that gets managed. The informal integration, the relationships, the cultural norms, the unwritten rules about how decisions get made, is the part that gets assumed. Organisations that manage only the formal integration often find that two years after the merger, the two legacy organisations are still operating as separate entities with a shared org chart.
Mistake four: not agreeing on what success looks like ¶
Most integration programmes have a set of milestones. Fewer have a clear definition of what the integrated organisation should look like when the integration is complete. Without that definition, it is impossible to know whether the integration has succeeded. The definition does not need to be elaborate. It needs to be specific enough that the leadership team can look at the organisation in twelve months and agree on whether it has been achieved.
Mistake five: treating communication as a one-time event ¶
Integration communication is often treated as a series of announcements: the deal is done, the new structure is announced, the new leadership team is introduced. What is less common is sustained communication about how the integration is progressing, what has changed, and what is still being worked through. The absence of this communication creates a vacuum that is filled by rumour and anxiety. Regular, honest updates, even when the news is that things are taking longer than expected, are more useful than polished announcements.
If you are currently in a post-merger integration and approaching the three-month mark, it is worth pausing to assess whether the structural changes you have made are showing up in actual decisions. A scoping call costs nothing and takes thirty minutes.