Home

›

Your First 90 Days as a Manager: A Month-by-Month Guide

Your First 90 Days as a Manager: A Month-by-Month Guide

What each month of your first ninety days is for, why the grace period matters, and what to review at day 90.

There is a window at the start of a management job when nobody expects you to have the answers yet. It does not last. Somewhere around the third month the questions stop being “how are you settling in” and start being “why is your team behind”. What you do in that window decides how the rest of the year goes, and most first-time managers spend it doing the wrong things for understandable reasons.

This is a guide to the ninety days, month by month. It is the structure behind The First-Time Manager’s 90-Day Journal, and it works whether or not you have the journal in front of you.

The grace period is real, and it is shorter than you think

New managers get roughly a quarter of tolerance. During it, you can ask obvious questions, admit you do not know how something works, and change your mind in public. All three get more expensive later.

The mistake is treating that tolerance as time off. It is not a rest period, it is an access period. You will never again be able to ask your team what they actually do all day without it sounding like an accusation. Use it while asking is still free.

Month one: Survive and Observe, weeks 1 to 4

The job in the first month is to understand the situation you have inherited, and to change almost nothing while you do it.

That is harder than it sounds, because the pressure runs the other way. A new manager wants to show they deserve the role, and the fastest way to look decisive is to fix something in week one. Nearly every one of those early fixes is aimed at a problem you have misdiagnosed, because you have not yet seen the constraint behind it. The process that looks stupid usually exists because something worse happened once.

What the first month is actually for:

  • The work. What your team produces, for whom, on what deadlines, and where it gets stuck.
  • The people. One conversation with each person, early, with real questions rather than a welcome speech.
  • The expectations above you. What your own manager will judge you on in six months, asked directly rather than inferred.
  • The inheritance. What was already broken before you arrived, and what everyone has quietly stopped mentioning.

Write it all down as you go. Not for a report. For yourself, because in week four you will compare it against what you now believe and find that a third of your first impressions were wrong. That comparison is the single most useful thing a new manager can do, and it is impossible without a record.

Two pieces of the first month have enough in them to deserve their own treatment: what to do in your first week, and how to run the first one-on-one with each person. If you were promoted from inside, add a third: managing people who used to be your peers. And if the first weeks leave you feeling like a fraud, there is a concrete reason for it: imposter syndrome in your first management job.

Month two: Build and Implement, weeks 5 to 8

By week five you know enough to act. The second month is where you install the things that will still be running in a year: expectations, rhythm, and delegation.

Set expectations before you enforce anything

Most management problems that look like performance problems are expectation problems. Nobody told the person what good looked like, and then they were judged against it. Say what you expect, say it specifically, and say it before it matters. Then hold it. An expectation you set and do not enforce is worse than one you never set, because now everyone knows which of your statements are decorative.

Build the rhythm

A weekly one-on-one with each person, a short team check, and one closing ritual on Friday. That is enough. The value is not in the meetings, it is in the predictability: people stop saving up problems for a crisis because they know a slot is coming.

Start delegating results, not methods

This is where the new manager most often fails, and the reason is sympathetic: you were promoted because you were good at the work, so you know exactly how you would do it. Handing over the task while keeping the method is not delegation. It is supervision with extra steps, and it teaches your team that thinking is your job rather than theirs.

Ask for the outcome, the deadline and the constraints. Leave the route to them. They will do it differently from you, sometimes worse at first, and that is the price of ever having a team that works without you in the room. More on this in delegating results, not methods.

If you need to put the phase on paper for your own manager, a 30-60-90 day plan is the usual format, and it is more useful as a thinking tool than as a document.

Month three: Lead and Strategize, weeks 9 to 13

In the last month the unit of measurement changes. Until now you were being assessed on how well you were adapting. From here you are assessed on what your team produces.

Two things follow from that, and neither is comfortable.

The first is that you work for the company, not for your team. Looking after your people is a large part of how you get results, but it is not the objective. A manager who ends up representing their team against the organization has quietly changed jobs without telling anyone.

The second is the asymmetry. When the team fails, it is your failure, and you carry it upward without a list of names. When the team succeeds, it is theirs, and you say so in public. Managers who reverse that get short-term credit and long-term nothing, because people stop bringing them anything worth having.

The third month is also when you can finally make the changes you were itching to make in week one. You now know which of them were real.

What to do at day 90

Sit down with everything you wrote and answer four questions honestly.

  1. What did I believe in week one that turned out to be wrong?
  2. Which of my people do I still not understand?
  3. What am I still doing myself that somebody else should own?
  4. What have I been avoiding because it will be an unpleasant conversation?

The fourth one is the important one. There is always an answer, and the cost of it doubles every month you leave it.

Next, on what comes after the transition: leading a team for the first time.


The First-Time Manager’s 90-Day Journal turns this structure into thirteen weeks of pages you fill in, with a themed week, a mission on Monday and a debrief on Friday.

Frequently asked questions

What should a new manager focus on in the first 90 days?

Understanding the team, the work and what your own manager will judge you on, in that order. The first month is for learning, the second for installing expectations and a weekly rhythm, and the third for owning what the team produces.

How long is the grace period for a new manager?

Roughly one quarter. During it you can ask obvious questions and admit what you do not know at almost no cost. After about three months the same questions start to sound like gaps.

Should a new manager make changes in the first month?

Very few. Most changes made in week one are aimed at problems that have been misread, because the constraint behind them is not visible yet. The exception is anything actively on fire, such as a deadline in days or a person about to resign.

What should you review at the end of your first 90 days?

What you believed in week one that turned out to be wrong, which people you still do not understand, what you are still doing that someone else should own, and which unpleasant conversation you have been avoiding. The last one matters most.