You did not build this team. You inherited it — its habits, its grudges, its one person everyone quietly works around, and its way of doing things that nobody can quite explain but everybody defends. The temptation in the first fortnight is to start fixing. The risk is that you change something load-bearing before you understand why it was there. Most new managers are judged less on the bold moves they make early and more on the avoidable damage they do before they understand what they have walked into.
This is a practical guide for managers taking over an existing team — whether through promotion, a sideways move, or joining a new organisation. The principles hold whether you have inherited four people or forty.
Why an inherited team is harder than a new one
Building a team from scratch is its own challenge, but at least the slate is blank. An inherited team comes with history you were not present for. There is a previous manager — possibly beloved, possibly the reason half the team is updating their CVs — and you are being measured against them whether you like it or not. There are working relationships, informal hierarchies, and unwritten rules. There is at least one person who applied for your job and did not get it.
None of this is on the org chart. And the people who hold this knowledge have no particular incentive to hand it over quickly, because in the early weeks you represent uncertainty. Their working assumption, reasonable until proven otherwise, is that you might be about to make their working lives worse.
So the first job is not strategy. It is not even the work. It is understanding the system you have joined before you start adjusting it.
A framework worth knowing
Michael Watkins’ The First 90 Days, written for exactly this transition, makes one observation that reframes the whole period: the most common failure in a new role is acting before you understand, and the second most common is understanding endlessly and never acting. The work is to move deliberately through learning into action, not to skip either.
Watkins offers a diagnostic that is genuinely useful here — the STARS model, which describes the five situations you might be inheriting:
- Start-up — building something from nothing (less relevant to an inherited team, but sometimes a sub-team within it is effectively new).
- Turnaround — a team in visible trouble that knows it is in trouble.
- Accelerated growth — a team that works but needs to scale fast.
- Realignment — a team that was once successful, is drifting, but does not yet realise it.
- Sustaining success — a high-performing team where your main job is not to break it.
The reason this matters: the team that knows it is failing (turnaround) wants decisive action and will trust you faster if you provide it. The team that thinks it is doing fine but is quietly drifting (realignment) will resist exactly the same behaviour, because from where they sit, you are fixing something that is not broken. Diagnosing which situation you are actually in — and they are often different from what you were told in the recruitment process — determines almost everything about how you should behave.
The most dangerous inheritance is sustaining success, precisely because the instinct of a new manager is to make a mark. A team that is genuinely working does not need a mark made on it. It needs someone who can keep it working and resist the urge to justify their own appointment with unnecessary change.
The first two weeks: listen, and be seen to listen
Resist the meeting where you set out your vision. You do not have one yet, because you do not yet understand the team. What you can usefully do in the first fortnight is learn — visibly, systematically, and without drawing premature conclusions.
The single highest-value activity in the early weeks is a round of one-to-one conversations with every member of the team. Not appraisals. Not interrogations. A genuine attempt to understand each person’s world. A few questions that tend to be productive:
- What do you work on, and what do you most enjoy?
- What is working well here that I should be careful not to break?
- What gets in your way — the things that make the job harder than it needs to be?
- If you were in my position, what would you look at first?
- What do you want from me as a manager?
That last question matters more than it looks. Some people want close support; others want to be left alone and trusted. Asking early signals that you intend to manage the person in front of you rather than impose a single style on everyone.
Take notes. Look for patterns — when three people independently mention the same broken process, you have found something real. And resist the urge to fix anything in the meeting itself. “That’s useful, thank you — I’m hearing this from a few people and I want to understand it properly before I change anything” is a far stronger response than an on-the-spot promise you may not be able to keep.
Watch for the gap between what you were told and what you find
The person who hired you described this team in a particular way. Some of that description will be accurate. Some will be the previous manager’s blind spot, or an optimistic gloss, or simply out of date. Hold the official version lightly. The team will show you the real one within a month if you pay attention.
Trust is built through small, kept promises
You cannot demand trust, announce trust, or accelerate it with a personality. You earn it, slowly, by doing what you said you would do — repeatedly, in small visible ways, before you ask the team to follow you anywhere significant.
This is why the early “quick win” matters, but not for the reason most people think. The value of fixing one small, genuine irritation in the first few weeks — the meeting nobody finds useful, the report nobody reads, the tool that has been broken for months while everyone assumed it was someone else’s job to raise it — is not the productivity gain. It is the demonstration that you listen, and that listening leads to action. It tells the team that talking to you is worth their time.
Pick something small, real, and clearly within your power to change. Avoid grand restructures in the first month; they signal that you have already decided you know better, before you have earned the right to that view.
A word on the previous manager. You will be tempted, especially if they left a mess, to distance yourself from them — sometimes explicitly. Resist it. Criticising your predecessor to the team almost always backfires: some of them liked that person, some of them are the mess you inherited, and all of them are quietly calculating how you will talk about them to the next manager. Acknowledge what worked, be diplomatic about what did not, and let your actions draw the contrast.
Common traps in the first 90 days
Going native too fast. The opposite of changing everything is changing nothing — being so anxious to be liked that you adopt every existing practice uncritically and lose the outside perspective that was, partly, why you were brought in. Your fresh eyes have a short shelf life. Within a few months you will stop noticing the things that struck you as odd on day one. Write those observations down early, even if you act on them later.
Over-relying on your most willing informant. Every team has someone who befriends the new manager quickly and is generous with context. This is useful, and it is also a single, partial perspective — sometimes from the person with the most to gain from shaping your view. Triangulate. The quietest person in the team often has the most accurate read on it.
Confusing activity with progress. Restructuring the team, rewriting the processes, and launching three initiatives in month one feels like leadership. Often it is anxiety in a suit — the need to be seen doing something. Deliberate, visible learning is also leadership, and usually the more valuable kind this early.
Neglecting your own manager. In the rush to understand the team below you, it is easy to under-invest in the relationship above you. Agree explicitly, early, what success looks like in the first 90 days and how it will be measured. The new manager who assumes they know what their boss wants, and finds out at the three-month review that they were wrong, has wasted the cheapest opportunity they will get to align expectations.
Handling the person who wanted your job badly. If someone on the team applied for your role, address it — privately, directly, and early. Pretending it is not the case fools nobody. A short, honest conversation acknowledging the situation, expressing that you value what they bring, and being clear that you want to work well together does more than months of careful avoidance. Some will come round. Some will not, and you will at least know where you stand.
A rough shape for the 90 days
Every team is different, so treat this as a sketch rather than a schedule.
Days 1–30 — Learn. One-to-ones with everyone. Understand the work, the relationships, the processes, and the numbers. Diagnose which STARS situation you are actually in. Identify one or two genuine quick wins. Agree success measures with your own manager. Change as little as possible.
Days 30–60 — Test and plan. You now have hypotheses about what needs to change. Test them in conversation rather than by decree — “I’m thinking about X, what am I missing?” lets the people who know the terrain stop you from walking off a cliff you cannot see. Deliver the quick wins you identified. Begin shaping a clearer picture of priorities.
Days 60–90 — Act and set direction. By now you have earned enough trust and gathered enough understanding to set a direction and make the more significant changes — and to explain the reasoning in a way the team can engage with, because they have watched you listen first. This is the point at which the vision conversation you wisely avoided in week one becomes both credible and welcome.
The single biggest determinant of whether the next 18 months go well is not the brilliance of your eventual strategy. It is whether you spent the first 90 days earning the right to have it heard.
Related reading
- Leading teams — building trust, avoiding micromanagement, and motivating a team you did not assemble
- Team management — the practical mechanics of running team briefings, expectations, and day-to-day management
- Self-awareness — understanding the leadership instincts and blind spots you bring into a new role
Managers stepping into a new team who want to build their confidence in leadership, trust, and team development can find structured CPD pathways at SkillsCircle, developed by Accipio. For those looking to formalise their development with a recognised qualification, Aicura offers CMI-accredited leadership programmes, including levy-funded apprenticeship routes.