The Rootlet blog

Practical tips and guides from our instructors

Your first 90 days as a new manager: a practical guide

Rootlet

Wed, 04 Nov 2026

Your first 90 days as a new manager: a practical guide

You've been promoted to your first manager role. Congratulations. You may be sitting at the same desk with the same people, yet what counts as a good day has quietly changed. This guide breaks your first 90 days into three stages, with what to do in each, the questions to ask, and the mistakes worth avoiding, so you can settle in without rushing into changes you later regret.


The short version

  • Days 1 to 30, listen and learn: hold an introductory one-to-one with everyone in your team, agree with your own manager what success looks like, and learn the processes you're now responsible for.
  • Days 31 to 60, build and act: set up routines you can keep, deliver one or two small improvements your team has asked for, and deal with small problems while they're still small.
  • Days 61 to 90, share and look ahead: hand some work on, prepare the team for what's coming, and review how it's gone with your manager.

Write it down as a simple 30/60/90 day plan, share it with your manager and update it as you go. There's a one-page version you can copy near the end of this post.


What really changes when you become a manager

As a team member, you were judged mainly on your own work. As a manager, you're judged mainly on what the team achieves, and on how people feel while they achieve it. Results that used to show by the end of a shift now show over weeks and months.

That's why so many new managers fall back on doing the work themselves. Picture a shift leader who used to be the quickest person on the floor. When a backlog builds on their first day in charge, the instinct is to grab a scanner and start picking. Sometimes that's right, for ten minutes in a crisis. But if it happens every shift, nobody finds out why the backlog keeps building, and the team learns that the leader will always step in.

You don't have to stop doing the work altogether. Staying close to it keeps you credible. The difference is that you do it on purpose, not as a way of avoiding the less familiar parts of the job.


Days 1 to 30: listen and learn

Many new managers feel they have to prove themselves by changing things straight away. Usually the better first move is to listen. Your team knows what really slows the work down, what's been tried before and what they're worried about. You don't, yet.


Hold an introductory one-to-one with each person

Book a private conversation with everyone in your team in your first couple of weeks. Make it clear this isn't a performance review. It's a chance to understand them and how they see the team. Choose a few questions from this list:

  1. What do you enjoy most about your work here?
  2. What gets in the way of doing a good job?
  3. If you were in my seat, what's the first thing you'd change?
  4. What should I definitely not change?
  5. How do you like to be kept informed, and how do you like to receive feedback?
  6. Is there anything you'd like me to know about you or your situation?

Listen more than you talk, take brief notes and thank people for being honest. Try not to promise changes on the spot. Something like "That's really useful. I'm hearing from everyone first, then I'll come back with what I'm going to do" is honest and keeps your options open.


Agree what success looks like with your own manager

Don't guess what "doing well" means in your new role. Ask your manager what they'd expect to see by the end of your first three months, and how they'll judge it. For most new managers, success looks something like this:

  • The work gets done reliably, even on busy days and when you're not there.
  • People know what's expected of them and where to go for help.
  • Problems reach you early, not once they've become a crisis.
  • Your manager trusts you to handle things and to flag what you can't.


Learn the parts of the job that are new to you

Set aside time each week for the side of the role you've never had to think about before:

  • Policies you now apply, such as absence reporting, annual leave, expenses and health and safety. You don't need to memorise them, but you do need to know where they are and who to ask in HR.
  • Systems you now use as a manager, such as rotas, approvals and reports.
  • Team measures: what's tracked, how it's reported, and which numbers your manager watches most closely.
  • People matters: who's on probation, who has agreed adjustments or flexible arrangements, and any open issues your predecessor left behind.

If you had a predecessor, ask for a handover conversation. If not, ask your manager what you most need to know first. Your organisation's own policies and HR team should always be your first stop on people matters. For general, impartial guidance on workplace rules in Great Britain, Acas has free advice for employers and employees.


Days 31 to 60: build routines and act


Start a rhythm you can keep

Move from introductory chats to regular one-to-ones. A short meeting with each person every fortnight, kept to the same length for everyone, is far more useful than long meetings that keep getting cancelled. Many teams also benefit from a brief weekly huddle to share priorities and problems. Choose a rhythm you can still keep in your busiest week.


Deliver one or two quick wins

A quick win is a small, visible improvement, ideally one your team asked for in those first conversations. It shows you listened and acted, and that builds trust for bigger changes later. A good quick win is:

  • small enough to finish in a few weeks
  • something the team, not just you, sees as a problem
  • within your authority, or easy to get approved
  • low risk if it doesn't work perfectly

Think of fixing a printer that's been "reported" for months, updating an out-of-date script, tidying a confusing shared folder or moving a handover time that suits nobody. Be wary of big changes in disguise, such as rewriting the whole rota pattern in week six. Those need more listening first.


Deal with small problems early

If someone is regularly late logging on, or two colleagues keep clashing, have a calm, private, informal conversation now. Small issues are much easier to raise in week five than in month five, and raising them fairly shows the whole team what to expect from you.


Days 61 to 90: share responsibility and look ahead

By now you should know your team well enough to start handing work on. Pick a task you used to do yourself, choose someone it would help to develop, brief them clearly, agree how much they can decide on their own, and check in at agreed points rather than hovering.

Use this stage to look ahead too. Is there a busy period, a new system or a change in the team coming up? Start preparing people now, so it doesn't land as a surprise.

Finish with a review conversation with your manager. Bring evidence rather than impressions: what you said you'd do, what you did, what worked, what didn't and what you'll focus on next.


If you now manage friends or former peers

Being promoted from within a team is one of the hardest versions of this move. Your friendships don't have to end, but some things do have to change, and it helps to say so early and privately, before a difficult situation forces the conversation.

  • Agree new boundaries. No gossip about the team, confidential means confidential, and work decisions happen at work, not by message late at night.
  • Make fairness visible. Use clear, shared rules for rotas, holidays and overtime, spread interesting work across the team, and give everyone the same time with you.
  • Don't over-correct. Being harder on your friends than on everyone else isn't fair either. A useful check before any decision: "Would I make the same call for someone I don't know well?"
  • Talk to anyone who wanted your job. Acknowledge it without fuss, don't discuss the interview, and where it makes sense, offer real responsibility that suits their strengths. Then give them time.


Mistakes to avoid in your first three months

  • Saying "nothing's going to change". Some things will, and people will remember you said it.
  • Saying "management have decided". You're part of management now. Explain decisions in your own words.
  • Bluffing. "I don't know yet, but I'll find out by Friday" builds more trust than a confident guess.
  • Insisting on "the way I used to do it". Your way may not be the best way for everyone else.
  • Making a plan with forty actions. Three to six actions per stage is plenty. A long list won't survive your first busy week.


A one-page 30/60/90 day plan you can copy

Copy this into a document or spreadsheet, add your own dates, and note how you'll know each action is done.

StageFocusTypical actions
Days 1 to 30Listen and learnIntroductory one-to-ones with everyone, agree success with your manager, learn the key policies and systems, start a weekly huddle.
Days 31 to 60Build and actRegular fortnightly one-to-ones, deliver one or two quick wins, deal with small issues early.
Days 61 to 90Share and look aheadHand one task on, prepare the team for what's coming, hold a review with your manager.

Treat the plan as a working document, not a contract. Things will come up that you couldn't have known about in week one, and that's normal. Update it every Friday and share it with your manager.


Want a step-by-step version?

This guide draws on the early lessons of our Leadership for New Managers course. The course has 56 written lessons covering one-to-ones, feedback, coaching, delegation and difficult conversations, and it follows a fictional new team leader through their first 90 days. Every section has a practice pack, including a 30/60/90 day plan template and one-to-one agendas. You don't need any management experience to start, and if you're not managing yet, each task has an option you can complete using a past team or a volunteer role.


0 Comments

Leave a comment

Learn something new every week

One short, practical tip each Thursday, plus news when new courses open. Free, and you can unsubscribe in one click.

We'll never share your email. See our privacy policy.