Inheriting a team means taking management responsibility for people you did not hire, in a context you did not build, with dynamics you do not yet understand.
The first job is information collection, not change. You need to understand what the team actually believes about their work, their previous manager, their priorities, and each other. That understanding takes six weeks of structured listening. Changes made before then are based on incomplete information and often damage the trust you need to make the team work.
Key takeaways
- Schedule a 1:1 with every direct report in your first two weeks.
- Ask each person what the team should stop doing before you ask what it should start doing.
- Make no structural changes before the six-week mark unless something is actively failing.
- Tell the team explicitly what you will and will not change, and when you will decide.
Why it matters
A team you inherited has a history you were not part of. There are existing loyalties, grievances, workarounds, and informal power structures. None of these are visible in an org chart. The only way to surface them is to ask, specifically, and listen carefully to what is said and what is avoided.
The biggest mistake new managers make with inherited teams is demonstrating competence through change. They reorganize a process, kill a meeting, or shift a priority in the first few weeks to show they are action-oriented. This often signals to the team that the new manager is not interested in understanding what was built before they arrived. Trust is built by understanding first, not by moving fast.
Your predecessor's decisions, even the ones that look wrong from the outside, almost always made sense in context. Understanding why a decision was made is as important as evaluating whether to keep it. If you cannot explain the original reasoning, you are not ready to change the outcome.
How it works in practice
A six-week listening and assessment plan for an inherited team
-
Week 1: schedule 1:1s with every direct report
Schedule 30-minute 1:1s with every direct report. Ask each one: 'What is going well that I should know not to break? What is not working that nobody has fixed? What would you want a new manager to know about this team?' Take notes. Do not share your conclusions yet.
-
Week 2: review the team's work artifacts
Read the last three sprint retrospectives, the last quarter's goal notes, any open design docs or RFCs. Do not comment on them yet. You are building context so that your later observations are grounded in actual work, not first impressions.
-
Week 3: identify the informal leaders
These are the people others go to with questions, the people who explain decisions to the rest of the team, the people who set the actual norms. Ask them more questions. Their read on the team is often more accurate than the formal record.
-
Week 4: map stated priorities versus actual priorities
Write down what the team says their priorities are. Then look at their calendar and task list. The gap between stated and actual priorities is where most execution problems live. Do not address it yet. Document it.
-
Weeks 5 and 6: share your observations and ask for pushback
Share what you have seen, what you want to understand better, and what you are thinking about changing. Be specific. Ask the team to push back before you decide. Then decide, and tell them what you decided and why.
Common mistakes
Changing a process before you know why it exists
Every quirky process was solving a real problem at some point. If you eliminate it before you understand the problem, the problem comes back.
Treating the team's loyalty to the previous manager as a problem
It is information. If they liked the previous manager, find out what they valued. If they did not, find out what they want to be different. Either way, the loyalty is a signal, not an obstacle.
Running group meetings to assess the team before individual conversations
People will not tell you the truth about team dynamics in a group setting with their peers. Run the 1:1s first, without exception.
Promising to fix everything you heard in the listening tour
You will hear real problems. You cannot fix all of them. Say: 'I have heard this and I am thinking about it' rather than 'I will fix this.' Overpromising and underdelivering is worse than saying nothing.
What it sounds like
A new engineering manager, Guy, is in his first 1:1 with Merav, a senior engineer who has been on the team for three years.
Guy: “I want to start by understanding your experience before I try to change anything. What is the one thing about how this team works that you would be most disappointed to see go?”
Merav: “Honestly, the no-meeting Fridays. Daniel negotiated that two years ago and it is the only reason I get deep work done.”
Guy: “Good to know. That is not something I would touch without a strong reason and without asking you first.”
Questions managers actually ask
How do I handle it if the team is in crisis and I cannot wait six weeks to act?
Triage the crisis first, on its own terms. Stabilize what is actively failing. Then return to the listening process for everything that is not on fire.
What if the previous manager was well-liked and the team is grieving the transition?
Acknowledge it directly: 'I know Daniel was a big part of how this team worked. I am not trying to replace that. I am trying to build something that works for you going forward.' Then listen.
How do I assess individual performance when I am still in listening mode?
Look at outputs, not impressions. Review pull request history, on-call records, and closed tickets. Do not form performance opinions from first-impression conversations.
What do I do if I find out there is a serious performance issue on the team?
Gather the facts first. Review the existing record. If there is a documented history, read it before you act on anything. Do not re-open settled matters without new evidence.
How do I handle the team asking me what I plan to change?
Tell them: 'I am not going to make structural changes in the first six weeks. I want to understand what is here before I decide what to change. I will share my thinking in week five and ask for your input before I decide.'
Should I meet with my own manager more frequently during this period?
Yes. Weekly is appropriate for the first six weeks. You want to calibrate your initial observations against what your manager sees from above before you act.
See how Leap improves execution in your meetings
Leap sits in your meetings, captures decisions and owners in real time, and shows you where execution breaks down before the week is out.