Get 1 month of Premium free

Use the code at checkout

00Days
00Hours
00Mins
00Secs
Claim 1 month free

BlogTeam Management

The First 90 Days as a New Manager: A Checklist

Spend the first month listening and learning how the work actually flows, the second month fixing the one thing everyone already agrees is broken, and the third setting expectations and giving real feedback. Changing things in week one costs you the information you would have needed to change the right things.

The shift nobody warns you about

The job you were promoted for and the job you now have share almost nothing.

You were good at doing the work. You are now paid for the output of a group of people, most of which you will not touch. The instinct that made you good, seeing a problem and solving it yourself, is now the thing most likely to make you a bad manager.

70%Of the variance in team engagement is accounted for by the manager, according to Gallup's manager research.Gallup, State of the American Manager

That number is quoted constantly and usually without a practical reading. Here is the useful one: the things you do in the first ninety days set the pattern for how people behave around you for a long time afterwards. Not because of a grand plan, but because people are watching closely for what you reward, what you ignore, and whether it is safe to tell you bad news.

Month one: learn

  1. Meet everyone individually in the first week

    Thirty minutes each. What are you working on, what is working well, what gets in your way, what would you change if it were your call.

    Ask, then be quiet. This is the only period where people speak plainly, before they have worked out what you want to hear. Write down what they say.

    Week 1Listen far more than you talk
  2. Follow a piece of work end to end

    Pick one real thing and trace it from arrival to finish: who touches it, where it waits, what gets re-entered by hand, where it goes wrong.

    Org charts describe reporting. This shows you how work actually moves, which is what you are now responsible for.

    Week 2
  3. Find out how you are measured

    Ask your own manager what a good quarter looks like, specifically, and what would count as failure.

    Many new managers spend six months optimising something nobody was measuring. Asking directly in month one is far cheaper than finding out in a review.

    Week 2Ask plainly
  4. Start 1:1s properly, immediately

    Weekly, thirty minutes, in the diary permanently, with the agenda owned by your report rather than you.

    Starting these late is the most common early regret, because the relationship you need in month three is built in month one. Our guide to [running 1:1s that produce decisions](/blog/how-to-run-one-on-ones) covers the structure.

    Week 1Never skip two in a row
  5. Change nothing that is not causing harm

    Note everything you want to change. Act on almost none of it yet.

    You have less information now than at any future point. The exception is anything actively harmful, which you fix immediately and explain clearly.

    The hardest item on this list

Month two: fix one thing

By now you have a list. Resist working through it.

Pick the single thing that came up in the most conversations and that you can actually change, and fix it visibly. One completed fix does more for your credibility than five in progress, and it demonstrates that telling you about a problem leads somewhere.

Good candidates are usually structural rather than personal: a meeting that should not exist, an approval step that adds three days, a handover where information reliably gets lost, a report nobody reads. Bad candidates are anything requiring another department's cooperation in your first sixty days, and anything that is really a disagreement about strategy.

Then say what you changed and why, connecting it explicitly to what people told you in month one. That connection is the whole point. Without it, the fix reads as a decision you happened to make rather than evidence that being honest with you works.

This is also the month to start delegating properly, which for most new managers means deliberately not doing work you are faster at.

Month three: set the standard

The first two months were about understanding. This one is about being explicit.

Say what good looks like. For each person, what does a strong quarter contain? Vague expectations produce work aimed at a target only you can see, and then a difficult conversation later that neither of you should have needed.

Start giving real feedback, in the week things happen. Both directions. Feedback saved for a review is about the past; delivered in the next 1:1 it is about the work. Our guide to giving feedback that doesn't damage trust covers the structure, and the timing matters more than the wording.

Name any performance concern now, gently and clearly. If someone is struggling, month three is early enough to fix it and late enough that you have the evidence. Waiting until month nine turns a solvable situation into an entrenched one, which our guide to handling an underperforming team member covers in detail.

Write down how the team runs. The cadence, who decides what, what needs approval. New people should not have to reverse-engineer it, and writing it forces you to notice the parts that make no sense.

Mistakes that are hard to undo

Doing the individual work. Comfortable, visibly productive, and it leaves the team unmanaged while taking the growth opportunities away from the people who should have them.

Changing things in week one. Made with the least information you will ever have, and reversing one costs more than waiting would have.

Being everyone's friend. Understandable, especially when managing former peers, and it makes the first hard conversation far worse than it needed to be. Warmth and clarity are compatible; avoidance and warmth are not.

Protecting people from context. Withholding bad news to keep morale up removes their ability to make sensible decisions, and they usually know something is wrong anyway.

Saying yes to everything from above. Your job includes pushing back on behalf of the team. A manager who accepts every incoming request is not shielding anyone, they are just a conduit with a title.

Never talking about anything but work. A manager who does not know what their reports want next is guessing about the single thing that most affects whether they stay.

One final thing, mostly reassurance. Almost nobody feels competent at this within ninety days, and the ones who look like they do are often the ones doing the individual work instead. The target for the first quarter is not mastery. It is to understand the team properly, fix one real thing, and be someone people will tell the truth to.

Frequently asked questions

What should a new manager do in the first week?
Meet everyone individually, ask what is working and what is not, and change nothing. The first week is the only time people will tell you things plainly, before they have worked out what you want to hear.
Should a new manager make changes immediately?
Only if something is actively causing harm. Early changes are made with the least information you will ever have, and reversing one costs more credibility than waiting a month would have.
How do you manage people who were your peers?
Name it directly, once, with each person. Acknowledge that the relationship has changed, say how you intend to handle it, and ask what they need. Pretending nothing has changed is what makes it awkward for everyone.
What is the most common new manager mistake?
Continuing to do the individual work they were good at, because it is comfortable and visibly productive. It leaves the team unmanaged and, worse, it takes the interesting work away from the people who should be growing into it.
How long before a new manager should expect to feel competent?
Six months to a year is normal, and nobody says this out loud. The first ninety days are about not doing damage and learning what is true, not about demonstrating that you have it under control.
Danish Khan

Danish Khan

CEO & Founder, Siela

Danish Khan is the CEO and founder of Siela, an AI-native workspace where teams and AI agents run CRM, meetings, tasks, and daily work together on one shared context layer.

Connect on LinkedIn

Published