When you inherit a team, your first job is to understand it, not to improve it. Spend your first two to three weeks in one-on-ones, address anyone who wanted your job directly, fix one small thing people already complain about, then set expectations. Save structural changes for month three or later, once you have the context and the trust to land them.
Key takeaways
Inheriting a team is not a chance to prove how good you are. It is a chance to earn the right to lead them.
The clunky process you want to kill is often the workaround for a problem you cannot see yet.
Diagnose the situation yourself. What you were told about the team before you arrived is usually incomplete.
One early, low-risk win proves that listening leads to action. That is the credibility you spend on the harder changes later.
Pace yourself across the first 90 days, not the first 90 hours.
What makes inheriting a team different from building one?
When you build a team, you hire for fit, set the culture, and build the history together as you go. When you inherit one, you walk into the middle of a story you cannot fully see. The team has a rhythm, old wounds, and a way of working that was set long before you showed up.
You didn’t choose them. They didn’t choose you. And they are watching to answer one question: is this person going to make my work life better or worse?
This situation is common and almost nobody is trained for it. By some estimates, 50 to 60 percent of first-time managers receive no formal training at all when they step into the role, and CEB research puts the share of new managers who fail or underperform in their first 18 to 24 months at around 60 percent. Most people walk into an inherited team and improvise.
The stakes are higher than they look. Gallup’s analysis of engagement data across business units found that managers account for at least 70 percent of the variance in team engagement. How you handle the takeover is not a soft skill question. It is the main variable.
There is also a career argument. The managers who can walk into a messy established team and stabilize it are the ones who get handed bigger and messier teams. Senior leaders notice that skill because most people don’t have it.
Why do new managers rush the first change?
Because you were probably put in the role for being good at the work. So you look at how the team operates, you immediately see three things you would do differently, and the pull is to start changing them this week.
That is ego talking. Not in a villainous way. It is the belief that you have to claim something in order to be successful in the seat.
The opposite is true. When you change things before you understand them, you are telling the team that their experience doesn’t matter and that the way they have been working was wrong. You have not earned the standing to say that yet, and you are almost certainly missing context.
I watched this play out with a client whose new leader announced that the team’s CRM was unfamiliar to him and that they would be switching to one he knew. The team pushed back. There was no urgent problem with the old system. What started as “would you be open to” turned into a directive, and the whole team moved onto a tool that didn’t match their workflow.
The friction was the smaller cost. The bigger cost was the story the team told themselves: he made this call before understanding how we work, and he made it because it makes him look good and us look slow.
What happens when you tear out a process you don’t understand?
I coached a sharp manager who took over a team after the previous lead left on bad terms. In his first two weeks, he wanted to reorganize the workflow and move people around, because from the outside it looked inefficient.
The step he wanted to remove was the one thing holding together a fragile handoff with another department. He didn’t know that. Nobody had told him.
We talked it through and he decided to run a test instead of a rollout. During the test, the process broke and the other department escalated. He got lucky in the timing. He was about to make a foolish move based on a system he had only seen from the outside.
They reverted quickly, and he waited about six months before touching that workflow again. In those months the team told him why the step existed and what risks needed handling first.
He wasn’t wrong that the process was clunky. He was wrong about when to touch it and how. Without the test run, he would have spent months rebuilding trust he could have torched in days.
What should you say to an inherited team on day one?
Keep it short and do not over-promise. Even if the interview panel asked for your vision and your five-point plan, day one is not when you deliver it. You have not met the team yet.
It should sound closer to this:
“I’m glad to be here. I know I’m stepping into a team that already knows how to do the work, so my first job is to understand how you operate before I change anything. I’ll be setting up time with each of you over the next couple of weeks.”
That message does a lot of quiet work. It signals humility, it tells them you are not about to detonate what they built, and it lowers the threat level in the room enough for real conversations to happen.
What kind of team did you actually inherit?
Before anything else, diagnose the situation yourself. Assume a gap between what you were told and what is actually happening, because there usually is one, and because a leader who can explain their own read of the team is far more credible than one repeating someone else’s summary.
Michael Watkins’ transition framework works well as a gut check here. In his Harvard Business Review piece on picking the right transition strategy, he sorts new-leader situations into categories including turnaround, realignment, and sustaining success. The category sets your speed.
A turnaround gives you permission to move fast, because things are genuinely broken and people know it. They want out of the turmoil. A high-performing team is the opposite: your job in month one is mostly not to break it. Same role, completely different speed.
Read it wrong and you either sit still while the team is begging for direction, or you come in swinging at a team that was doing fine.
Most teams are somewhere in the middle, and often different parts of the same team sit in different categories. One workflow is in turmoil while another is humming. Those need different approaches from you.
How do you run a listening tour that works?
In your first two to three weeks, sit down one-on-one with every person on the team. The talking ratio should tilt heavily toward them. You are taking notes, asking real questions, and letting your own silence prompt them to keep going.
Five questions that consistently surface the real picture:
What’s working well that I should be careful not to change?
What’s frustrating you or slowing you down?
If you were sitting in my seat, what’s the first thing you’d fix?
What do you want me to know about how you like to work?
What are you worried I’m going to do?
That last one is awkward, which is exactly why it is valuable. It pulls the fear into the room where you can actually address it.
Three rules for these conversations:
Stay neutral on your predecessor. The moment you pile on, you have taught the team that you talk about people behind their backs. They will assume you do it about them too. Listen, empathize, acknowledge, and do not pick sides in week one.
Take notes, and consider recording with permission. Good notes let you connect patterns across conversations you would otherwise miss. They also let you say, six weeks later, “you told me this in our first conversation, and here’s how it shaped this decision.” That is what caring looks like in practice.
Open by handing them the floor. Not your resume. Try: “I want to use this time to understand your world, so I’m mostly going to ask questions. If you have questions for me at the end, I’m happy to take them.” People are braced for a new boss to talk about themselves. When you do the opposite, they relax and you learn more.
What do you say to the person who wanted your job?
Nearly every time you inherit a team, someone on it applied for the role you got. Do not pretend that isn’t happening.
I have watched managers tiptoe around that one person for months while the tension sits there and poisons everything. Both of you know. Name it instead:
“I know you were up for this role. I imagine it’s a strange situation to now figure out how to work with me in this seat. I’d like us to work well together, and I want to hear what would make that work for you.”
One conversation will not fix their disappointment. But naming it directly takes most of the bad air out of the room, and it demonstrates something they will remember: you lead by addressing hard things rather than avoiding them.
What counts as a good early win?
Somewhere in your listening tour, the same small frustration will come up more than once. A recurring meeting nobody needs. A tool the team has asked for and never received. An approval step that takes three days for no reason.
Pick one of those and fix it fast. Small, low risk, low hanging. Not a structural change dressed up as a quick win.
This does something a big move cannot. It proves you listened, and it proves that listening leads to action. That is real credibility, and it is what you spend later on the bigger, harder changes.
How do you set expectations without criticizing the past?
Once you have listened, state your standards plainly and without apology. Frame them forward, not as a verdict on how things used to run.
Something like: here’s what I care about and how I like to operate, here’s what I’ll be paying attention to, and here’s what success looks like for this team over the next quarter.
You are not saying the old way was wrong. You are saying here is where we’re going now. People can follow that. Ambiguity is the enemy, and it is worth being more explicit than feels necessary.
When should you make your first real change?
After you have listened, built some trust, and understood the context. By then you have earned the standing to lead a change rather than impose one.
When you make it, communicate the why clearly. People get behind a change they understand far more willingly than one that appears in their inbox one morning with a rationale that reads like a press release.
A rough rhythm that works:
Weeks 1 to 3: listening, almost entirely
Month 2: fix the small things, set expectations
Months 3 to 5: structural changes, once you have the context and trust to land them
There is no prize for fastest reorganization. If you feel pressure to prove yourself, pause and ask where it is coming from. Usually it is your own head, not your team and not your boss.
This matters more right now than it used to. A lot of teams are in the middle of an AI transformation, which means more managers are inheriting teams and being asked to change how they work at the same time. That combination is exactly where rushing does the most damage.
The managers who rush in to make their mark spend the next year cleaning up the damage. The ones who slow down at the start move much faster for years afterward, because they built the trust to do it.
You don’t earn a team’s respect by being impressive in week one. You earn it by proving, repeatedly, that you make their work better.
FAQ
What if my boss expects visible changes in the first 30 days? Make the diagnostic work the visible deliverable. Tell your boss you will bring back a read on the team by day 30, including what you are changing and when. That is a change plan, and it buys you room to avoid a structural move before you understand the system.
Does the listening tour work the same way on a remote team? Yes, with two adjustments. Book 45 minutes instead of 30, because rapport takes longer on video. And do not batch all the calls into one week, so you have time between conversations to notice patterns.
What if I inherit a team of former peers? Name the change in role explicitly in the first one-on-one rather than hoping the relationship carries over unchanged. Former peers usually need to hear what stays the same and what does not, particularly around information you can no longer share with them.
What if the team openly misses the previous manager? Let them. Loyalty to a former leader is evidence the team is capable of loyalty, which works in your favor later. Do not compete with the predecessor and do not criticize them, even when the team invites it.
What if there is a known underperformer on the team? Do not act in the first month unless there is a safety or integrity issue. Use the listening tour to understand whether the person is underperforming or is stuck inside a broken process, then address it directly once you have the context and the standing.
This is the kind of moment we work in depth inside the Leadership Accelerator, Archova’s 12-week cohort program for new and early-stage managers. If you want the free version first, start with the masterclass on leading as a new manager or the book, The Confident & Competent New Manager.
