Acquisitions create a unique blend of opportunity and uncertainty for engineering teams. Whether your company is acquiring or being acquired, your team faces questions about job security, technology choices, cultural changes, and their role in the combined organisation. This guide covers how to lead your team through an acquisition while preserving the talent and momentum that made the team valuable in the first place.
Navigating the Uncertainty Period
Acquisitions involve extended periods of uncertainty - between announcement and close, between close and integration, and during integration itself. Your team will have questions you cannot answer, and this ambiguity is deeply uncomfortable for engineers who thrive on clear, logical problem-solving.
Be transparent about what you know and do not know. Do not speculate about decisions that have not been made, and do not offer reassurances you cannot guarantee. Instead, share the timeline for when decisions will be made and commit to communicating updates as soon as you have them.
Focus the team on what they can control. Day-to-day engineering work continues regardless of the acquisition. Maintaining productivity on current projects provides stability and demonstrates the team's value to the combined organisation. A team that delivers through uncertainty is more likely to be prioritised in integration decisions.
- Be transparent about what you know without speculating about unmade decisions
- Share timelines for when decisions will be made and follow through on updates
- Focus the team on controllable factors - current projects, quality, and delivery
- Maintain regular one-on-ones to address individual concerns privately
Planning Technology and Team Integration
Technology integration is one of the most complex aspects of an acquisition. Decisions about which systems, tools, and platforms to retain, migrate, or retire have profound implications for both teams. Advocate for decisions based on technical merit and business needs rather than politics or organisational hierarchy.
If you are involved in integration planning, take time to understand the other team's systems before proposing changes. What looks like legacy from the outside may have sound engineering reasons. Approach integration with curiosity and respect rather than assumptions about whose technology is superior.
Plan for a transition period where both sets of systems run in parallel. Forced rapid migration introduces risk and demoralises the team whose systems are being retired. Allow time for knowledge transfer, testing, and gradual migration to minimise disruption to users and engineers.
Navigating Cultural Differences
Every engineering organisation has its own culture - how decisions are made, how risk is managed, how quality is defined, and how people interact. Acquisition brings together teams with potentially different cultural norms, and these differences can create friction if not addressed intentionally.
Identify cultural differences explicitly rather than letting them cause confusion. One team may favour formal design reviews while the other prefers informal peer discussion. One may have a conservative deployment approach while the other deploys continuously. Neither is inherently better - discuss the differences openly and decide together which practices to adopt.
Protect the elements of culture that make both teams effective. The acquiring company often assumes its culture should be adopted wholesale, but the acquired team's culture likely has valuable elements worth preserving. Advocate for a thoughtful blend rather than a one-sided adoption.
Retaining Key Talent Through the Acquisition
Acquisitions are a significant flight risk for top talent. Uncertainty, potential loss of autonomy, and competing offers from companies eager to hire engineers from disrupted teams all contribute to attrition. Proactive retention efforts are essential.
Identify your key people early and have candid conversations about their concerns and aspirations. Understand what would make them excited about the combined organisation and what might cause them to leave. Work with leadership to secure retention incentives - financial bonuses, role clarity, project ownership, or reporting structure preferences.
Show key people their future in the combined organisation. Engineers who can see a compelling career path, interesting technical challenges, and a team they want to work with are far more likely to stay than those facing ambiguity about their role. Paint a clear and honest picture of what lies ahead.
Key Takeaways
- Be transparent about what you know and do not know - avoid speculation and false reassurances
- Advocate for integration decisions based on technical merit, not organisational politics
- Address cultural differences explicitly and preserve valuable elements from both organisations
- Proactively identify and retain key talent through candid conversations and visible career paths
- Maintain team productivity during uncertainty to demonstrate value to the combined organisation
Frequently Asked Questions
- How do I manage my team when the acquiring company has very different engineering practices?
- Start by understanding their practices before judging them. What seems rigid or chaotic from the outside may have sound reasoning behind it. Identify the practices that are non-negotiable for each side and the areas where there is flexibility. Propose a phased approach to alignment that gives both teams time to adapt. Where practices conflict, propose experiments to determine which approach works best rather than defaulting to the acquiring company's way.
- What if I am being acquired and unsure about my own role?
- Focus on what you can control - leading your team well through the transition. Your ability to maintain team productivity, facilitate integration, and retain key talent demonstrates your value to the combined organisation. Have direct conversations with your new leadership about your role and expectations. If your role is genuinely at risk, prepare for that possibility while continuing to lead effectively.
- How do I integrate two teams with different technology stacks?
- Do not rush technology consolidation. Run both stacks in parallel while you evaluate which to retain for each use case. Involve engineers from both teams in the evaluation to ensure fair assessment and buy-in. Consider that different use cases may be best served by different technologies. Create a multi-year roadmap for consolidation with clear milestones and regular reassessment points.
Download Acquisition Integration Templates
Access our acquisition management templates including integration planning frameworks, cultural assessment tools, and retention strategy playbooks for engineering managers.
Learn More