8 Lessons from Leading a Team You Inherited

Taking over an existing team requires a different playbook than building one from scratch. The trust a founder earns by hiring someone doesn’t transfer automatically to a leader who simply shows up one day in charge — it has to be built from zero, often while the team is quietly watching to see if you’re worth following. That gap matters more than most new leaders expect: employees who strongly agree they trust their organization’s leadership are roughly four times more likely to be engaged, and 58% less likely to be actively job searching, according to Gallup research. Get the transition right, and you inherit a running start. Get it wrong, and you inherit the exit interviews six months later.

Most leaders aren’t set up well for this moment either — 82% of managers step into a leadership role having had no formal management or leadership training at all, per Chartered Management Institute research, which means most people are figuring out “how do I lead people I didn’t choose” in real time, under real stakes, with no playbook.

So we asked people who’ve actually done it — founders, CEOs, and leadership consultants who’ve taken over teams they didn’t build — what genuinely worked. Here are eight lessons, straight from their own experience.

At a Glance: 8 Lessons on Leading an Inherited Team

What These Leaders Learned the Hard Way

There’s no single formula here — but a pattern still runs through all eight lessons: none of these leaders started by asserting authority. They started by understanding what was already working, then acted in a way the team could actually see and trust. Here’s how each of them approached it.

Observe First Then Tweak Delivery

The instinct with any inherited team is to reorganize fast, so it feels like yours. Most of the time, that instinct is wrong — the team already knows things about the work, the client, or the process that a new leader simply hasn’t learned yet. Here’s what RHILLANE Ayoub thinks:

The instinct with an inherited team is to reorganize it fast so it feels like yours. That is usually the wrong move. When RMD picked up a client account in France that came with two freelancers already embedded on it for over a year, I almost rebuilt their whole workflow in week one to match how we run things out of Tanger. I held off instead.

I spent the first three weeks watching before changing anything: who the client actually picked up the phone for, and why one weekly report never got opened no matter how good the data in it was. Turned out the reporting format was the real problem, not the people. The freelancers were doing solid work. They just were not presenting it in a way the client could read in five minutes between meetings.

So I kept both of them and only changed the report to match our monthly call structure. The account renewed at the end of that year. Here is the lesson: “not how I would have built it” is not the same thing as “broken.” An inherited team already knows things about the client that you do not. Spend the first month finding out what those things are before you touch the org chart.

RHILLANE Ayoub, CEO, RHILLANE Marketing Digital

Fix Real Pain Fast

Listening builds goodwill, but listening alone doesn’t build trust — a team that’s been let down before is watching for whether a new leader will actually do something with what they hear. Here’s what Ankush Gupta thinks:

When I took over the team at our ORM work, I walked into a group that had been running client engagements for months without me. They had their own rhythms, their own ways of handling accounts, and zero reason to trust that I wouldn’t disrupt what was already working.

The first thing I did was nothing. For two weeks, I just watched. I sat in on client calls. I read through old Slack threads. I asked questions that started with “walk me through how you handle this” instead of “why don’t we do it this way.” The team had been burned before by leaders who showed up with a playbook before understanding the work, so I made it clear I wasn’t that person.

Then I focused on one thing: removing friction they’d been complaining about for months. Our task follow-up system was a mess. People were chasing each other across three different tools, and nothing escalated properly when someone dropped the ball. I built a simple automation using Google Sheets and Google Chat webhooks that sent graduated reminders and escalated to me on the fourth strike. It solved a real problem they’d named, and I shipped it in 48 hours.

That’s when credibility started. Not from a vision deck. From fixing something broken.

The second move was expectation-setting, but not in a meeting. I wrote a short doc that outlined what I expected from each role, what they could expect from me, and what decisions I would make versus what I would defer to them. I made it clear I wouldn’t touch client relationships they owned unless they asked me to. Then I sent it in Slack and said, “Read this. If anything feels wrong, let me know.” Three people flagged things. I adjusted. That document became the operating agreement.

Here’s what I learned: you don’t earn credibility by being the smartest person in the room. You earn it by proving you understand the work they do, that you’ll protect what’s working, and that you’ll fix what’s been ignored. An inherited team doesn’t need a hero. They need someone who listens before they act.

Ankush Gupta, Fractional CMO, Fameninja ORM Management Company

Earn Authority Through Visible Results

Some leaders take the opposite risk from moving too fast — they listen for so long that the team quietly stops expecting anything to change. Here’s what Runbo Li thinks:

I’m Runbo Li, Co-founder & CEO at Magic Hour.

The single most important thing when leading a team you inherited is to earn authority through competence, not through title. People who were there before you have their own rhythms, loyalties, and skepticism. They’re watching to see if you’re going to impose process for the sake of control or actually make things better.

Back at Meta, I joined the New Product Experimentation team where everyone had been building together before I showed up. I was the new data scientist dropped into a group of engineers and designers who already had strong opinions about what to build next. My instinct was to prove value fast, so within my first two weeks I shipped an analysis that changed the direction of a product decision. Not because I was trying to show off, but because I genuinely found something no one had looked at yet. That single artifact bought me more trust than any intro meeting or “getting to know you” coffee chat ever could.

Here’s the principle: inherited teams don’t need you to “align” them. They need you to demonstrate that your presence makes the work better. I call it “proof before permission.” You show the result first, then people give you the latitude to lead.

The mistake most people make is spending weeks doing a “listening tour” without producing anything. Listening is fine. But if all you do is listen for a month, the team quietly decides you’re a tourist. You have to pair curiosity with output. Ask questions AND ship something meaningful in the same breath.

The other thing I’d say is, don’t try to change the culture on day one. Culture is downstream of results. Win a few battles alongside the team, and the culture will bend toward you naturally.

Inherited teams are not a disadvantage. They’re a cheat code, because the talent is already assembled. Your only job is to point it somewhere worth going and prove you belong at the front.

Runbo Li, CEO, Magic Hour AI

Empower Quiet Connectors You Discover

Every team has an informal structure sitting on top of the formal one — and the people who quietly hold it together aren’t always the ones with the senior titles. Here’s what Sahil Kakkar thinks:

We see an inherited team as an ecosystem rather than a blank page. Before making changes we learn who people trust and who others turn to for help. Titles do not always show who has influence. We look for people who keep work steady and help others understand how things get done.

We learned this when progress seemed slow on a team we took over. At first we thought the issue was execution. After listening closely we found a manager who connected departments and understood the team’s unwritten processes. We involved that person in planning and gave their knowledge more weight which improved coordination and showed us why listening should come before change.

Sahil Kakkar, CEO / Founder, RankWatch

Align Around One Measurable Outcome

A team that’s used to operating in silos doesn’t need more meetings — it needs one shared target everyone can see and measure themselves against. Here’s what Arvind Sundararaman thinks:

My best advice is to act as a conductor: quickly align the inherited team around one clearly defined business outcome and agree on 30, 60, and 90 day success metrics so everyone knows what to aim for. A specific moment that taught me this was before a major AI launch, when I asked sales, product, data, and compliance to sign off on the same success criteria and measurement plan. After launch we kept a tight cadence of joint reviews of telemetry, user behavior, and risk rather than letting each function work in isolation. That shared ownership turned the work from a collection of projects into an operating model that sustained adoption.

Arvind Sundararaman, AI & Data Platform Leader

Celebrate Hidden Strengths Foster Trust

Before deciding who should stay or go, it’s worth asking a different question first: what is this team already quietly good at that no one has ever said out loud? Here’s what Vaibhav Kakkar thinks:

When we lead a team we did not hire, we do not begin by asking who should stay or go. We first look at what the team already does very well but no one has clearly recognized. Many inherited teams build quiet strengths while solving daily challenges. When we give those strengths clear meaning, people feel valued instead of judged, and trust starts to grow.

We once inherited a team with a reputation for moving slowly. After listening carefully, we saw they were thoughtful because rushed decisions often caused bigger problems later. We described that strength as disciplined judgment and shaped our work around it. The team gained confidence, performance improved naturally, and we learned that respect often creates better results than pressure.

Vaibhav Kakkar, Founder and Group CEO, Digital Web Solutions

Redesign Context to Break Habits

“That’s the way we’ve always done it” sounds like resistance, but it’s rarely a conscious choice — and treating it like one is often where new leaders go wrong. Here’s what Cristina Furlan thinks:

The most honest advice I can give to anyone leading a team they inherited is to stop asking the wrong question.

The wrong question is: how do I get these people to change? It’s wrong because it assumes the resistance comes from a conscious choice. It almost never does.

When I became a manager in the aeronautical industry at 33, the phrase I heard most often was “that’s the way we’ve always done it.” At first I read it as closed-mindedness. Then I realized I was looking in the wrong place.

What I was seeing wasn’t identity — it was conditioning. And that distinction changes everything, because the two require completely different responses.

Identity is something you build. Conditioning is something that’s done to you — years of reinforcement, hierarchies, and repeated expectations that become automatic over time. People who say “that’s the way we’ve always done it” aren’t defending a position. They’re executing a response learned so deeply they no longer recognize it as one. It’s not resistance to change. It’s the invisibility of change — they can’t see the alternative because the system they’ve operated in for years never showed it to them.

That shifts the entire job of the leader.

Persuasion doesn’t work — conditioning can’t be argued out of existence. It has to be de-conditioned. And you de-condition it by changing the context, not the people. You create situations where the old way of operating simply stops producing the expected results — not by mandate, but by evidence. When people reach the conclusion on their own, they’re not giving in. They’re updating a mental model that no one had ever challenged before.

The most significant moment in my own experience wasn’t when someone changed their behavior. It was when someone said, for the first time, “I never thought it could be done differently.” That’s not an outcome — it’s proof that the conditioning has loosened enough to let a new possibility in.

A leader who inherits a team doesn’t need authority. They need architectural patience — the ability to redesign the context with enough precision and steadiness that change becomes inevitable, without ever feeling imposed.

Change people choose holds. Change people endure doesn’t.

Cristina Furlan, Author | Founder, The 4S Method of Adaptive Intelligence™, The 4S Method of Adaptive Intelligence™

Ask What Remains Unseen

Sometimes the fastest way to understand a new team isn’t more observation — it’s a single direct question, asked plainly. Here’s what Gabriel Shaoolian thinks:

My advice: just ask the team what they think you don’t understand yet. In those exact words. I did this with a team I inherited early on, and it helped me understand the everyday dynamic, unspoken tensions and underlying challenges more easily.

It cut down on time because it gave me more answers in one meeting than weeks of my own observations would have. I see leaders trying to prove they understand everything from the moment they walk in. But when you’re new to a certain environment, you obviously won’t know everything from the get-go. Admitting the gap and asking the team to fill it in themselves is a good starting point.

Gabriel Shaoolian, CEO and Founder, Digital Silk

Frequently Asked Questions

How long should you observe before making changes to an inherited team?

There’s no universal number, but most of the leaders above waited two to four weeks of active listening before making a significant change — long enough to understand real patterns, short enough to avoid being seen as passive. The exception is fixing an already-named, obvious pain point, which several leaders addressed within days.

How do you earn trust from a team you didn’t hire?

Through visible, credible action, not through the title itself. The clearest pattern across all eight lessons is pairing genuine listening with a real fix, decision, or result the team can actually see — trust follows evidence, not announcements.

What’s the biggest mistake leaders make with inherited teams?

Two opposite failure modes show up equally often: reorganizing too fast before understanding what’s already working, and listening so long that the team decides nothing is going to change. The lessons above suggest the fix is doing both at once — observe and act, rather than picking one phase and finishing it before starting the other.

Should you keep the team’s existing processes or rebuild them?

Start from “not how I’d have built it” being different from “broken.” Several of the leaders above kept core processes intact and only changed the specific piece that was genuinely causing friction, rather than rebuilding from scratch.

The Real Takeaway

None of these eight leaders led by asserting control. They led by finding out what the team already knew, fixing what was genuinely broken, and letting results — not titles — do the convincing. If you’ve just inherited a team, avoiding the more common leadership mistakes in the first 90 days pairs naturally with these lessons, and building the broader leadership skills that matter going forward will only make the transition steadier. Trust doesn’t come with the title. It comes after.

Sources

• Kinkajou Consulting: Top Leadership Development Statistics 2026 — Gallup trust/engagement data; Chartered Management Institute training-gap statistic