Leading a Team You Didn’t Build


people sitting on chair in front of table while holding pens during daytime

Between 27% and 46% of leadership transitions are considered failures or disappointments within two years, according to McKinsey research on successful transitions. The number is worse for frontline managers: CEB Global found that 60% fail within their first 24 months. The common thread in most of those failures isn’t incompetence. It’s the assumption that the skills which earned the promotion are the same skills the transition demands.

Every manager eventually inherits a team. You get promoted and suddenly lead the people who were your peers yesterday. You transfer into a department that’s been running without you for years. You replace a manager who left, and the team has opinions about it. In each scenario, the team has a history, a rhythm, and a set of unwritten rules that existed before you walked in. The question isn’t whether you’re qualified. It’s whether you’re willing to learn the room before you try to change it.

The Transition Is the Job

Michael Watkins surveyed more than 1,300 senior HR leaders for his research at IMD Business School, and nearly 90% agreed that transitions into new roles are the most challenging times in a leader’s professional life. Nearly three quarters said that success or failure in the first few months strongly predicts long-term outcomes.

That tracks with what I saw across two decades in IT operations leadership. Every time I stepped into a new leadership role (and there were several, from team lead to Director to fractional COO work at Ops Harmony), the first 90 days were never about proving I belonged. They were about learning what the team already knew that I didn’t.

Watkins uses the term “breakeven point,” typically around three months, to describe the moment when you contribute as much value as you consume. Before that point, you’re a net drain on the team’s productivity, regardless of your title. The faster you accept that framing, the faster you reach it.

What the Team Knows That You Don’t

An inherited team holds institutional knowledge you can’t find in any documentation. They know which processes work on paper but fail in practice. They know which stakeholders follow through and which ones don’t. They know the real reason the last initiative stalled.

When I took over an operations team during a major infrastructure rollout in 2011, the outgoing manager’s transition notes were three pages long. Useful, but they covered maybe 10% of what mattered. The other 90% lived in the team’s heads: vendor relationships, escalation shortcuts, which approvals were pro forma and which required actual political capital.

This is the core mistake most new managers make. DDI’s Frontline Leader Project found that 70% of frontline managers weren’t even expecting the promotion. Many react by immediately asserting authority through new processes, schedule changes, or strategy shifts. The team reads every one of those moves as a verdict on their prior work.

The Listening Tour That Actually Works

“Do a listening tour” is advice so common it’s nearly meaningless. Most managers treat it as a checkbox: schedule 30 minutes with each person, ask about their role, nod, move on. Real active listening requires more structure than that.

A useful listening tour requires three specific questions, asked one on one, in the first two weeks:

“What’s working that I should be careful not to break?” This question signals respect. It tells the person you assume there are things worth preserving. The answers also give you a map of the team’s invisible infrastructure: the informal processes, workarounds, and communication habits that keep things running.

“What’s one thing that frustrates you that nobody’s fixed?” This surfaces the small, solvable problems that build trust when addressed. Not the strategic vision items. The broken things. The approval that takes three days when it should take one. The meeting that everyone attends but nobody finds useful.

“What should I know about this team that won’t show up in any report?” This is the question that produces the real information. Dynamics between team members. History with previous leadership. Sensitivities around specific projects or decisions. You won’t get the full picture from any single person, but the pattern across conversations tells you where the real terrain is.

Reading the Team’s History Without Rewriting It

Gallup’s 2026 State of the Global Workplace report found that managers account for 70% of the variance in team engagement. That’s a heavy number, and it cuts both ways. If the team is functioning well, the previous manager did something right. If the team is struggling, the damage predates you.

Either way, your first task is diagnosis, not treatment.

I learned this during a fractional COO engagement with a mid-size services firm through Ops Harmony. The team had what looked like a productivity problem: missed deadlines, inconsistent output, low energy in meetings. My instinct was to restructure their workflow. Instead, I spent two weeks sitting in on their existing meetings and reviewing three months of their project history. The real issue wasn’t workflow. It was that two senior team members had an unresolved conflict from a failed project six months earlier, and it was poisoning every interaction. No process change would have fixed that. A conversation did.

Resist the urge to audit the team’s performance in your first month. You don’t have enough context to evaluate anyone fairly. Watkins calls this “learning before you lead,” and it applies whether you’re inheriting a high-performing team or one that’s clearly struggling.

Your First Real Decision

At some point, usually between weeks three and six, you’ll face a decision that signals to the team who you are as a leader. It might be approving or rejecting a budget request. It might be handling a difficult conversation between two team members. It might be deciding how to respond to pressure from above.

McKinsey’s research found that when transitions succeed, nine out of ten teams meet their three-year performance goals, with 13% lower attrition and 5% higher revenue than average. The common thread wasn’t that these leaders made bold strategic moves early. It was that their early decisions demonstrated consistency, transparency, and respect for the team’s context.

Pick your first visible decision carefully. Make sure it’s informed by what you learned during your listening tour. Explain your reasoning to the team, because giving clear direction matters more when people don’t yet know how you think. If the decision changes something the team was doing before, acknowledge what existed and why you’re adjusting. “I noticed X, I talked to several of you about it, and here’s what I think we should try” lands differently than “Starting Monday, we’re doing Y.”

When to Change Something (and When to Wait)

The 60-day mark is where most inherited-team transitions go right or wrong. By then, you’ve listened, you’ve observed, you’ve made a few small decisions. The question becomes: what’s worth changing, and what should stay?

A practical filter: change things that cause daily friction for the team and require your authority to fix. Leave things that are working, even if they’re not how you would have designed them.

DDI research found that 57% of employees have quit a job because of their boss. That statistic makes more sense when you consider how many new managers walk into a functioning team and immediately start rearranging furniture. The team doesn’t leave because the new process is bad. They leave because the message behind the change is “what you were doing wasn’t good enough.”

The changes that build credibility are the ones that solve problems the team already identified. Remember the frustrations they surfaced during your listening tour. Pick one or two. Fix them visibly. That earns you more trust than any strategy deck.

The Long Game

Inheriting a team is not a problem to solve. It’s a relationship to build.

The managers I’ve watched succeed at this (and the transitions I’ve navigated myself) share one quality: patience combined with genuine curiosity about how things work. Not passive patience, where you avoid decisions. Active patience, where you invest the time to understand before you act.

Gallup’s data shows that manager engagement has dropped nine points since 2022, and every five-point decline cascades to roughly 21 million workers disengaging at the team level. The managers holding steady are the ones who recognize that their first job isn’t to lead. It’s to earn the right to.

Your team was there before you. They’ll remember whether you honored that.

Ty Sutherland

Ty Sutherland is an operations and technology leader with 20+ years of experience. He is Director of IT Operations at SaskTel, founder of Ops Harmony (fractional COO and EOS Integrator), and former COO at WTFast. He writes Management Skills Daily to share practical management frameworks that work in the real world.

Recent Posts