In an acquisition, the initial priority isn't strategy, but calming uncertainty. Leaders should establish a constant, accessible communication flow—using tools like chat communities and an open-door policy—to reassure the team and ecosystem, addressing stress before tackling operational changes.
Related Insights
Don't just hand an integration plan to functional leaders post-close. Involve them early in the process as co-architects. Their input is crucial for validating financial models and strategic assumptions, ensuring realistic expectations and fostering ownership of the deal's success.
A counterintuitive benefit of being acquired by a larger company is improved internal team cohesion. The sudden influx of new partnerships and opportunities from the acquiring entity can compel the smaller team to work more closely together, fostering stronger alignment and mutual support.
To ensure Day 1 alignment and retain key talent, treat integration planning as a collaborative process. Share the developing integration plan with the target's leadership during due diligence. This allows them to validate assumptions, provide critical feedback, and feel like partners in building the future company, rather than having a plan imposed on them.
Instead of arriving with a rigid 100-day plan, CPC advises using the initial post-acquisition period to build trust. The management team is exhausted from the sale process. Forcing immediate, top-down changes is a mistake; the priority should be establishing vulnerability and mutual understanding for long-term success.
When an acquisition supplants an internal project, the messaging is crucial for morale. Position the internal team's work as a successful R&D phase that validated the market need and informed the "buy" decision. This celebrates their contribution and frames the acquisition as an acceleration of their validated strategy.
To maintain momentum, Cisco makes critical integration decisions—like site strategy or system consolidation—during diligence, not after close. These decisions are embedded into the final deal commitment materials, preventing post-close paralysis and emotional debates, allowing teams to execute immediately.
To reassure an acquired company's partners, communicate that their existing investments (like competencies and specializations) will be directly transferred. Describing the program integration as a 'lift and shift' provides concrete assurance that their earned value will not be lost, reducing uncertainty and maintaining trust.
During a merger, prioritize people over process. Technical integration is secondary to building trust between teams. Use simple, cultural activities like joint happy hours and "show-and-tells" about the tech stack to humanize the engineering effort and foster empathetic collaboration early on.
Cisco treats the deal announcement and the deal close as two distinct moments with different goals. "Announce Day" is for leadership to present a joint strategic vision and secure employee buy-in. "Day 1" (the close) is for celebrating, distributing swag, and beginning the tactical onboarding process.
When handling an outage or escalation, the biggest threat to customer trust isn't the problem, but a chaotic internal response. Instill a "clarity over chaos" rule by designating one leader, one channel, and one message. A calm, owned response builds more credibility than a hundred smooth weeks.
