Inheriting a team - whether through a reorg, a promotion, or a new role - presents unique challenges. The team has existing dynamics, unwritten rules, established relationships, and possibly unresolved issues from their previous manager. Your job is to learn the landscape, build trust, and gradually make improvements without disrupting what is already working well.
Assessing the Team You Have Inherited
Spend your first two to four weeks in assessment mode. Meet with every team member individually to understand their role, their goals, their concerns, and their perspective on the team's strengths and weaknesses. These conversations are the most valuable investment of your early weeks.
Talk to the team's stakeholders - product managers, designers, and other engineering teams - to understand how the team is perceived externally. The gap between the team's self-assessment and their stakeholders' assessment often reveals important issues.
Review the team's recent work: their velocity trends, incident history, code quality metrics, and delivery track record. This data provides an objective baseline that complements the subjective insights from your conversations.
Building Trust with the Inherited Team
The team may be wary of you. Their previous manager may have left under difficult circumstances, or they may have had a great manager and resent the change. Either way, trust must be earned through consistent behaviour over time - it cannot be declared or assumed.
Be transparent about your approach. Share what you are learning, what you plan to change, and what you plan to keep. Explain your management philosophy and values so the team knows what to expect from you. Predictability builds trust.
Honour existing commitments made by the previous manager whenever possible. If the previous manager promised someone a project, a promotion, or a schedule accommodation, follow through. Breaking commitments - even ones you did not make - signals unreliability.
Navigating Existing Team Dynamics
Every team has informal power structures, alliances, and tensions that exist beneath the surface. Identify the informal leaders - the people the team turns to for guidance regardless of their title - and build strong relationships with them. Their support is essential for any changes you want to make.
Be cautious about taking sides in existing conflicts. Listen to all perspectives before forming opinions, and avoid being co-opted by the first person who shares their version of the story. Early judgements based on incomplete information can permanently damage your credibility.
Resist the urge to reorganise immediately. Even if you see structural problems, changing team composition or responsibilities in your first few weeks creates anxiety and resentment. Wait until you understand the full picture before making structural changes.
Implementing Change Thoughtfully
Start with changes that have high impact and low controversy - fixing a broken process, addressing a long-standing blocker, or improving a tool that everyone complains about. These early wins demonstrate your commitment to making the team better and build the credibility needed for more significant changes later.
When making larger changes, involve the team in the process. Present the problem you have observed, share your proposed solution, and invite feedback. Changes that the team helps shape are adopted more readily than changes imposed from above.
Communicate the reasoning behind every change. Teams that understand why something is changing are more receptive to the disruption. If the change is motivated by your assessment, share the data and observations that led to your conclusion.
Addressing Issues Left by the Previous Manager
You may discover unresolved performance issues, broken processes, or damaged relationships that the previous manager neglected. Address these, but approach them with empathy - the team may not even realise these are problems if they have been normalised.
Avoid publicly criticising the previous manager, even if their management was poor. Speaking negatively about an absent person signals to the team that you might do the same about them. Focus on what you are going to do differently rather than what was done wrong before.
If the team had a great previous manager, do not try to replicate their style. Be authentic to your own management approach. The team will adjust to your style as long as it is consistent, fair, and effective.
Key Takeaways
- Spend the first weeks in assessment mode - meeting people, understanding dynamics, and reviewing data
- Build trust through transparency, consistency, and honouring existing commitments
- Identify informal leaders and existing dynamics before attempting to make changes
- Start with high-impact, low-controversy changes to build credibility for larger improvements
- Address legacy issues with empathy and avoid criticising the previous manager
Frequently Asked Questions
- How quickly should I make changes to an inherited team?
- Unless there is an urgent crisis, wait at least four to six weeks before making significant changes. Use this time to understand the team, build relationships, and identify the highest-priority improvements. Quick changes based on incomplete understanding often create more problems than they solve. The team will appreciate a thoughtful approach over a hasty one.
- What if the team openly resists my leadership?
- Resistance is a natural response to change, especially if the team was close to their previous manager. Do not take it personally. Continue to be consistent, transparent, and fair. Have individual conversations to understand the source of resistance - often it is driven by fear or grief rather than a genuine objection to you. Over time, consistent positive behaviour overcomes most resistance. If specific individuals remain actively hostile after sustained good-faith effort, address it as a performance issue.
- Should I keep the previous manager's processes or introduce my own?
- Keep what works, change what does not, and involve the team in both decisions. Do not change processes simply because they are not your preferred approach - if the team is functioning well with existing processes, preserve them. Change processes that are clearly broken, outdated, or ineffective, and explain why the new approach will be better. The goal is team effectiveness, not personal preference.
Download Team Assessment Templates
Access our team assessment templates, stakeholder interview guides, and 90-day transition planning frameworks for managers inheriting existing teams.
Learn More