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.

Address cultural issues by applying product management principles. Use surveys to gather data and identify pain points, then empower the team to propose solutions. Test these ideas like product features and iterate based on what works, making culture-building a shared, active process.

Successful large-scale acquirers remain nimble, flexing their own processes to suit the acquired company rather than force-fitting it into a rigid corporate structure. This preserves the culture and talent that made the company valuable, preventing value destruction and keeping the new team engaged.

Departments like IT and Operations often operate with conflicting perspectives. True alignment requires more than sharing views; it needs "microtranslation," where each leader explains their goals in the context of the other's world to co-create solutions.

'Culture add' is insufficient if new hires with different perspectives remain siloed. The goal should be 'culture multiply,' fostering intentional interaction and mutual influence between new hires and the existing culture. This creates a dynamic tension that fosters growth, rather than just filling a gap.

Changing an entrenched culture is daunting. The best approach is to start small. Identify a group of ambassadors, run a focused pilot project aligned with the desired new culture, learn quickly, and use its success to spread change organically rather than forcing a large-scale overhaul.

Instead of trying to merge broad cultural concepts, identify the target's key practices—like specific events or community work—and consciously continue them post-close. This maintains continuity and respects the acquired team’s identity far more than a values presentation.

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.

During M&A integration, conflict arises when teams defend their respective solutions. Re-center the conversation on the customer problem they both aimed to solve. Emphasizing that all solutions are temporary and fungible de-escalates conflict and fosters alignment around a shared, permanent goal.