My program had 50 entities in 23 countries and one deadline. Then, mid-flight, came the merger.
A merger doesn’t move the plan. It moves the ground the plan stands on. The mandate was a Europe-wide compliance rollout: 50 companies, 23 active countries, a regulatory deadline that was not up for negotiation. We were in the middle of delivery, pilot plus four waves, when the group acquired a second business. Overnight the list held 70 entities, not 50.
The first question in the room was the obvious one: do we even need to take on the 20 new ones? Perhaps they had had their own solution for ages. They had none. Two years earlier, during preparation, we had spoken with exactly this group, then still an independent house. They said they had an open flank in the field and were preparing decisions. With the acquisition they stopped those preparations. The buyer already had something. That something was my program.
The comfortable reaction would have been to replan everything. One shared framework, one shared deadline, 70 entities on a single curve. It sounds like order, and it is a mistake.
I kept the 50 on their original deadline. Pilot and four waves ran through as planned, on scope, on time, on budget. The 20 new ones got their own curve at their own pace, four waves through November 2026, three of which are now done. The client backed this split; we planned it ourselves and found it a home inside the acquisition’s integration program.
Why the split is not a given
A shared deadline for 70 entities would have meant making the 50 finished countries wait for the 20 unfinished ones. That costs no budget. It costs something more expensive: a country that could deliver and is held back on purpose stops believing that your next deadline is meant seriously. In a program, credibility is the one currency you cannot reprint. Give up a firm deadline once for the sake of appearances, and afterwards you are left with wish-dates.
The 20 new ones ran differently from the 50 for another reason. Different technology, different organization, and a young, agile unit that had been carved out of a larger group not long before. It feared the grip of the big, slow-moving buyer. And the first thing we turned up with was a conservative compliance program that makes postings and business travel more expensive, slower and more cumbersome. As a show of good faith, that counts for little. Before anything regulatory could move there, trust had to come first.
What I underestimated
With the merger, legal authority moved from the outside in. Before, it sat with an external advisory firm; afterwards, with the group itself. I underestimated that when responsibility moves, the work moves with it. Where someone else used to supply the legal groundwork, the concepts, the decision papers and a good part of the alignment now sat with us in the program. There was no work package for it. The load shifted quietly, and it only became visible once the ball was already with us.
In hindsight, that is the real lesson of this merger. The 20 new entities were the visible part. The shifted ground beneath them was what actually made the work.
When the ground shifts in the middle of a program, first check what has moved beneath the plan. And keep what can already deliver on its deadline.
A merger rarely moves the plan. It moves what the plan stands on. Start trying to rescue the plan in that moment, and you are rescuing the wrong thing.
