The clock starts before close
Integration planning is often treated as a post-close workstream, staffed after the deal is announced and the operating teams have already begun improvising. By the time the plan lands, the organization has answered dozens of questions on its own, and unwinding those answers costs more than making them would have.
The teams that hold their synergy case tend to have done the unglamorous work early: a named integration lead before signing, decision rights mapped before close, and an explicit list of what will deliberately not be integrated in year one.
Decision rights are the long pole
Systems consolidation is visible, expensive, and easy to plan for. It is rarely what stalls an integration. What stalls it is ambiguity about who decides, on pricing, hiring, product roadmap, and customer escalations, in the overlap between two organizations that both had answers before the deal.
Ambiguity here does not announce itself. It shows up as slow decisions, and then as attrition among the people who were most able to make them.
Ambiguity about who decides does not announce itself. It shows up as slow decisions, then as attrition.
Tanvir Islam, Chief Operating Officer
Move fast on the reversible
A useful sorting rule: separate the decisions that are expensive to reverse from the ones that are not, then move immediately on the second category and take the time to get the first right.
Most integration paralysis comes from treating every decision as if it were in the first bucket. Very few are.
