The First 90 Days: Taking Over a Team Without Breaking It

Taking over a team is the highest-leverage moment in a manager's career, and the easiest one to botch. A new manager walks in with two handicaps: the team does not trust them yet, and the team knows things the manager does not. The first ninety days decide whether that gap closes or widens. Get them right and you inherit a working machine. Get them wrong and you spend a year repairing the damage.

The good news is that the playbook is well known. The bad news is that almost nobody follows it, because the instincts it requires feel wrong. Here is the version that works.

1. Listen Before You Touch Anything

The first instinct of a new manager is to prove competence by making changes. That instinct is a trap. Every change you make in the first month is a change made without information, and the team knows it. They are watching to see if you understand their world before you rearrange it.

For the first two weeks, do nothing but listen. Meet every team member one on one. Ask three questions and nothing more: what is working, what is not, and what would you change if you were me. Do not fix anything you hear, however tempting. The point is not to solve problems, it is to build the map of the territory. The team will test you, quietly, to see if you actually listen. Pass the test before you take any other action.

2. Find the Two Realities

Every team has two realities: the official one and the operational one. The official one lives in the roadmap, the org chart, and the status reports. The operational one lives in the daily workarounds, the whispered frustrations, and the tasks that never appear in any plan.

Your job in the early weeks is to reconcile them. Which processes on paper are ignored in practice, and why? Which people carry the load that the org chart assigns to someone else? Which "urgent" projects are actually dead but too polite to be buried? The gap between the two realities is where the real work of the next year lives.

3. Make Only Promises You Can Keep

New managers overpromise because they want to be liked, and being liked feels like the foundation of trust. It is not. The foundation of trust is reliability: doing what you said you would do, and saying clearly what you cannot do.

In the first ninety days, make very few commitments and keep every single one. If you promise to unblock a request by Friday, unblock it by Friday. If you cannot fix the legacy problem this quarter, say so plainly and explain the trade-off. A manager who delivers on two small promises a week builds more trust than one who announces ten grand plans and delivers two.

4. Identify the Informal Leaders

The org chart says who reports to whom. It says nothing about who the team actually follows. Every team has informal leaders: the senior engineer whose opinion shapes the rest, the veteran who knows where the bodies are buried, the connector who carries gossip and trust in equal measure.

These people are not your rivals, they are your early-warning system. Find them in the first month and recruit them, not with flattery but with genuine respect: ask their opinion, share your reasoning, give them credit in public. If the informal leaders decide you are serious, the rest of the team follows within weeks. If they decide you are a threat, no amount of formal authority will save you.

5. Change One Thing, Deliberately

By the end of the first ninety days you should have made exactly one visible change, and it should be carefully chosen. Not the biggest problem, but the problem whose fix is unambiguous and whose benefit the whole team can feel.

This is the proof-of-competence move. It tells the team that you noticed something, understood it, and fixed it cleanly. It creates the pattern: this manager finds real problems and solves them. The second change comes easier, and the third easier still. The first one is the only one that is hard, because it is the one that establishes the pattern.

6. Set the Rules of Engagement

Early on, define how you work, explicitly and briefly. How do you want to hear about problems, in advance or after the fact? What is your response time on messages? How do decisions get made, by you, by the team, or by whoever owns the area? Write it down and share it. Most team friction comes from mismatched expectations, not from bad intentions.

The rules do not need to be heroic. They need to be stated. Teams tolerate almost any working style once it is predictable. What they cannot tolerate is a manager whose behaviour is a mystery they have to decode.

7. Deliver the Honest Assessment

Somewhere around day seventy, sit down with your own manager and give them the assessment they have been waiting for: what is actually going on in the team, what is good, what is broken, and what you plan to do about it. This is the moment the ninety days pay off, because you now know what you are talking about.

The assessment should be honest enough to be uncomfortable. If the team has a performance problem, name it. If the roadmap is fantasy, say so. The credibility you built by listening and delivering small wins is exactly what makes this conversation possible. A new manager who reports only good news is a new manager who will not be trusted with bad news, and the bad news always comes.

8. What Ninety Days Buy You

The first ninety days do not produce a transformed team. They produce something more valuable: a platform. You know the real problems. The team knows you listen and deliver. The informal leaders are on your side. The rules of engagement are explicit.

From that platform, the changes you make in the following year have a chance to stick, because they are made from knowledge and trust instead of authority and guesswork. The managers who fail in the first year are almost never the ones who made the wrong changes. They are the ones who made changes before they had earned the right to make any. The first ninety days are how you earn that right.

Tags

#management #leadership #career