Your first 90 days as a new manager

You just became a manager, and your instinct is to keep proving you're good at the job you used to have. So you take the hardest problem yourself, you rewrite someone's work instead of giving feedback on it, and you fill your first 1:1s with status updates because that's the meeting you know how to run.

This article covers what actually changes when you get the title, and the conversation to have with each person in your first week. It also covers how much to change and how much to leave alone, the operating cadence to set up early, and a 30/60/90 outline. Read it once before your first week, then come back to the 30/60/90 section at the end of each month.

The advice comes from Julie Zhuo, former VP of Design at Facebook and author of The Making of a Manager; Camille Fournier, author of The Manager's Path and former CTO of Rent the Runway; Claire Hughes Johnson, former COO of Stripe; and Nikhyl Singhal, who ran product teams at Meta and Google. The templates come from the Mochary Method's published curriculum, which is free to read and copy.

What actually changes when you become a manager

You used to be measured on what you produced. Now you're measured on what your team produces, which sounds obvious until the first week you personally shipped nothing and had to decide whether that week was a success. Handing work off is the skill this depends on, and our delegation playbook covers how to do it without hovering.

The Mochary Method's manager guide states the goal in one line: make your team maximally productive. Everything in your first 90 days should be judged against that, including the parts that feel like they aren't real work.

Fournier goes on in the same answer to say that management is a service job, and that you're serving the team and the company. Her warning is aimed at people who expect to keep the freedom of a senior IC and add authority on top of it. You don't get either of those in the first 90 days. What you get is interruptions, other people's deadlines, and a lot of meetings you didn't schedule.

The other thing that changes is that nobody handed you a manual. Zhuo wrote her book because she couldn't find one for the situation she was in.

Later in that answer she adds that nobody had ever explained to her what a manager is or what doing the job well looks like. If you feel unprepared in week one, that's how nearly everyone starts, and it doesn't mean you were promoted by mistake. Zhuo also says the theory is the easy part and applying it every day is where it gets hard, because the right move changes depending on who you're talking to.

The first conversation with each person on your team

Book 45 minutes with every report in your first week. Don't run it as a status meeting. The point is to learn how each person works, what they're worried about, and what they want from you, and to tell them the same about yourself.

Start with yourself, because your team is going to spend the next month figuring you out anyway. Tell them how you like to be told bad news, how quickly you answer messages, what you'll want to be looped in on, and what you'd rather they just decide.

Hughes Johnson calls these personal operating principles, and she puts them at the front of her book about company building because a manager who can't describe their own tendencies makes everyone else guess. You don't need a polished document in week one. Four or five honest sentences about how you operate will do, and you can correct them later when you learn you were wrong about yourself.

The Mochary Method's Magic Questions give you a version of this you can reuse every month. People rate a set of areas from 1 to 5, including their life at work, their personal life, working with their peers, and working with you. Then you take the lowest number and ask what would move it up one point. The Magic Questions doc has the full list.

Asking "what's it like to work with me" in week one will feel strange when the answer is "I've known you for three days." Ask anyway. It sets up the habit of your reports telling you things about yourself, which is the habit that saves you in month six. If you want the view from the other side of that table, our guide to the first 1:1 with a new manager is written for the report, and it's a good preview of what the person across from you is preparing.

Earning the right to give direction

You have the authority from the first day, and people still decide separately whether they'll let you help them. Nikhyl Singhal, who has managed product teams at Meta and Google, describes the second big mistake new managers make as assuming the org chart is the same thing as a mandate.

His practical version is to open with "what can I help you with" and accept that some people will say they don't need you. He says that's fine, because anything he says after that will be annoying and will backfire. He waits until they need help, then picks one or two areas and works closely on those.

A minute earlier in the same answer, Singhal gives the model he prefers for how a manager shares control. Handing the work over completely and taking it back completely are both wrong. He describes riding in the sidecar of a motorcycle while the other person drives: attached whether he likes it or not, with a specific job of giving counsel.

For your first 90 days that means you pick your spots. Find one thing each person is stuck on and help with that one thing, all the way through. Helping with one real problem does more for you than a lot of advice nobody asked for.

How much to change in your first month

New managers arrive with a list of things that look broken. Some of them really are broken. Others are the result of a tradeoff someone made two years ago for a reason nobody wrote down. You can't tell which is which in week one.

Spend the first month asking why things are the way they are before you change them. When you find something that seems wrong, ask the person closest to it what would happen if you changed it. You'll get three kinds of answer: nobody knows why we do this, we do this because of a constraint that's gone, or we do this because of a constraint that's still here. Only the first two are yours to fix quickly.

The exception is a person problem. If someone on the team is failing, or two people can't work together, or your predecessor told someone six months ago they'd be promoted and nothing happened, that doesn't improve while you get oriented. Take it to your manager in your first two weeks and ask for the history before you act.

Areas of Responsibility, from the Mochary curriculum, is the fastest way to find the unclear ownership. You list every function your team performs and put exactly one name next to each. The gaps and the duplicates show up immediately, and the exercise gives you a reason to ask a lot of basic questions in your first month. The AOR doc has the template and the warning about single points of failure.

Setting up your operating cadence

Your team is already absorbing one big change, which is you. Try not to make everything else unpredictable at the same time. The most useful thing you provide in the first 90 days is a rhythm people can count on.

She gives examples like setting quarterly or monthly goals, and says these rituals feel like process but work as a source of stability, because when everything else goes sideways the team already knows how decisions get made. You need three of them in your first 90 days: 1:1s, a team meeting, and a written update.

Protect the 1:1s above everything else. Fournier is generally against the number of one-on-ones people hold, and she still draws a hard line around this set.

Her argument in the rest of that answer is that meeting one-on-one with every peer and stakeholder doesn't scale as your team grows, and that a lot of those meetings happen with people who never wanted them. The ones with your reports are different. Cancelling those teaches your team that you'll drop them whenever your week gets busy.

Weekly is the right default while you're new. The Mochary manager guide suggests starting weekly to build rapport and set norms, then dropping to every other week once you show up and find there isn't enough new material. Give the meeting a standard shape so nobody has to invent an agenda on the spot.

The issue format is worth stealing exactly as written. The Mochary Issue / Proposed Solution template asks for the issue, what the person did to help create the situation, and a proposed solution. That middle question is the one that changes the meeting, because it moves the problem to something the two of you can act on. The full agenda structure, including how to handle actions people didn't complete, is in the 1-1 Template and Instructions, and the Manager Training Basics outline shows how the pieces fit together.

Your other two rituals are simpler. Run one team meeting a week where the whole group sees the same numbers and the same open decisions. Send one short written update to your manager and your peers every week: priorities, what changed, what's at risk, and the one thing you need from someone else. Both of those give you an excuse to notice problems before they reach you as emergencies. Keep your own 1:1 with your manager on the calendar too, and use our guide to one-on-ones with your manager to run it, because you need someone you can tell that you don't know what you're doing yet.

When you got promoted from inside the team

Managing people who were your peers last month is the hardest version of the first 90 days. You have friends on the team, you have history with everyone, and now you write their performance reviews.

Name the change out loud in your first week, once, with each person. Pretending nothing happened doesn't work, because everyone already knows something happened and they're waiting to see whether you'll acknowledge it.

Two things go wrong from here, and they pull in opposite directions. The first is overcorrecting, where you go cold with people you used to eat lunch with to prove you're impartial. The second is avoiding the authority entirely, where you never give hard feedback to a friend and the rest of the team notices within a month. Both are obvious to everyone else on the team. Run the same 1:1 structure and hold the same feedback standard for every person, and stay as direct with your friends as you always were.

Expect to lose some things. You'll stop being the person people complain to about management, because you're management now. Some of those friendships will change. Assume it takes a full quarter for the team to work out who you are in this role.

Mistakes that show up in the first 90 days

• Doing the work yourself. The fastest way to feel productive in week two is to take the hardest task. It teaches your team you don't trust them and it eats the time you need for everything else. Pick the task you'd most like to keep and give that one away first.
• Reorganizing before you understand the current setup. Structure changes are expensive and hard to reverse. Wait until you can explain why the current one exists.
• Saving up feedback for the review cycle. By the time the review cycle arrives, the person has forgotten the specifics and it sounds like you were storing it up. Give it within a few days, in a 1:1, with the specific example. Our guide on giving feedback that people can act on has the wording.
• Announcing you have an open door and stopping there. Nobody brings a new manager a real problem unprompted. You have to ask specific questions repeatedly before people believe you want the answer.
• Passing your manager's decisions along without a view. If you deliver every decision as "they told us to," your team learns you have no influence upward. Say what you argued for and what you'll do about the parts you disagree with.
• Cancelling 1:1s when you get busy. This is the one your team will remember at the end of the quarter.
• Trying to be liked. People tend to like managers who are useful and predictable. If you go after being liked directly, you'll avoid the conversations that matter.
• Hiding that you're new. In week three you can say "I don't know yet, I'll find out by Thursday" at no cost at all. Guessing and being wrong is much more expensive.

A 30/60/90 plan you can adapt

Treat this as a default to edit, not a schedule to follow exactly. If your team is in the middle of a crisis, most of days 1 through 30 compresses into the first week.

Frequently asked questions

What should a new manager do in the first week?

Hold a 45-minute conversation with each report, tell them how you work before you ask how they work, and put weekly 1:1s and a team meeting on the calendar. Don't change any process in week one. Spend the time learning why things are the way they are.

How much should a new manager change in the first 90 days?

Change your own behavior immediately, change unclear ownership and obvious blockers early, and leave process, team structure, and the inherited roadmap until you can explain why they exist. The exception is a person problem, which gets worse while you wait.

Should a new manager still do individual contributor work?

Some, at first, and less every week. Keep enough hands-on work to stay credible with your team and hand off anything the team depends on. If you're still the critical path on a project in month three, your team can't deliver without you and you have no time to manage.

How do I manage people who used to be my peers?

Say the awkward thing out loud once in your first week, then be consistent: the same 1:1 structure for everyone, the same feedback standard, and the same directness you had before. Going cold on people to prove you're impartial is just as obvious to the team as playing favorites.

What are the most common first-time manager mistakes?

Doing the work yourself instead of delegating, saving feedback for the review cycle, reorganizing before understanding the current setup, canceling 1:1s when the week gets busy, and passing along decisions from above without saying what you think.

How do I know if my first 90 days went well?

Your team knows what they're accountable for, they bring you problems before those problems become emergencies, you've given every person real feedback at least once, and you've delivered one result without being the person who did the work. Ask your manager directly for their assessment rather than guessing.

Nobody trained me. Is that normal?

Yes. Julie Zhuo wrote The Making of a Manager because she couldn't find anything written for someone who was an IC one week and had four reports the next, and Nikhyl Singhal describes people getting promoted into management without being taught the job. Pick one framework, run it for a quarter, and adjust.

The first 90 days on one page