The First 90 Days as a New Manager
/11 min read
The first 90 days as a new manager decide how your team will read you for the next two years. People form a working theory of their manager quickly and then look for evidence that confirms it. If your first month is a blur of reactive meetings and late nights fixing other people's work, the theory becomes "our new manager is a stressed senior engineer with a calendar problem". If your first month is calm listening, clear one to ones and a few visible fixes, the theory becomes "this person is going to make our work easier".
This guide gives you a week by week plan for all 13 weeks, a one to one template you can copy, worked examples of feedback using the SBI model, and a delegation matrix that stops you from quietly doing your old job on top of your new one. It is written for first time people managers with 3 to 10 direct reports, whether you were promoted from inside the team or hired from outside.
Why the first 90 days feel so hard
Most new managers were promoted because they were very good individual contributors. The skills that got them there (deep focus, personal output, being the person who knows the answer) start working against them on day one. Your output is now the team's output. A day where you wrote excellent code or closed a deal yourself but nobody on the team got unblocked is, from the job's point of view, a weak day.
Three traps show up again and again:
- The rescue trap. You see a piece of work going slower than you would do it and you take it over. It feels helpful. It teaches the team that you will step in, and it costs you the hours you need for planning and people.
- The silence trap. You avoid giving feedback in the first weeks because you want to be liked, then a small issue becomes a large one and the first real feedback conversation lands as a shock.
- The change trap. You arrive with a list of improvements and start shipping them in week two, before you understand why things are the way they are. Some of your changes break something invisible, and you lose trust you have not yet earned.
The plan below is built to avoid all three. It front loads listening, sets up a weekly rhythm early, introduces feedback in small doses and saves larger changes for the second and third month, once you have data.
The three phases of a new manager's first quarter
Think of the quarter in three blocks of roughly a month each.
- Weeks 1 to 4, learn. Meet everyone, understand the work, the stakeholders and the history. Make almost no structural changes. Fix only things that are clearly broken and cheap to fix.
- Weeks 5 to 8, set the rhythm. Agree on goals with your manager, write down team priorities, start regular feedback, begin delegating deliberately.
- Weeks 9 to 13, improve and prove. Make one or two meaningful changes based on what you learned, run a first round of development conversations, and review the quarter honestly with your manager.
A week by week plan for weeks 1 to 13
Use this table as a default. Your context will shift some items earlier or later, which is fine as long as the order of learning, rhythm, then improvement stays intact.
| Week | Focus | Concrete tasks | Evidence you are on track |
|---|---|---|---|
| 1 | Arrive and listen | Meet your manager to agree what success looks like at day 90. Book a first 45 minute one to one with every direct report. Read the last quarter of team documents, retros and incident notes. | Every report has a first meeting in the calendar. You have a written list of your manager's top three expectations. |
| 2 | First one to ones | Run the first meetings with four questions (below). Take notes in one place. Shadow the team's main recurring meetings without changing them. | Notes for every person, including what they want from their job in the next year. |
| 3 | Map the stakeholders | Meet the five to eight people outside the team who depend on it most. Ask what the team does well and what frustrates them. | A one page stakeholder map with each person's main need. |
| 4 | Write the listening summary | Summarise what you heard in themes, share it with the team, and ask if you got it right. Pick one small, visible fix (for example a meeting nobody values). | Team confirms or corrects your summary. One small fix shipped. |
| 5 | Agree on goals | Turn the listening summary into three team priorities for the quarter. Review them with your manager and the team. | Priorities written down and visible to the team. |
| 6 | Weekly rhythm | Move one to ones to a fixed weekly or fortnightly slot with the template below. Start a short weekly team update. | Two weeks of one to ones held on schedule. |
| 7 | First feedback | Give at least one piece of positive and one piece of constructive SBI feedback to each person, in private. | Feedback noted in your one to one log for every report. |
| 8 | Delegate on purpose | Fill in the delegation matrix for your own task list. Hand over two tasks you still do from your individual contributor days. | Two tasks owned by someone else, with a clear check-in point. |
| 9 | Development conversations | Ask each person where they want to be in a year and agree one growth goal. | A written growth goal for each report. |
| 10 | One meaningful change | Choose the change with the strongest evidence from weeks 1 to 4 (a process, a handoff, an on-call rule). Explain the why before the what. | Change announced with reasoning and a review date. |
| 11 | Stakeholder follow up | Go back to the stakeholders from week 3 and ask what has changed for them. | At least half of them can name something that got better. |
| 12 | Team retro on the quarter | Run a retro on how the team worked, not just what it shipped. Include your own behaviour as a topic. | Three agreed actions for next quarter. |
| 13 | Review with your manager | Compare outcomes to the day 90 expectations from week 1. Draft priorities for the next quarter. | A short written review, agreed with your manager. |
The four questions for a first one to one
- What is going well in your work right now, and what would you protect if you were me?
- What gets in your way most often?
- How do you like to receive feedback, and how did it go with previous managers?
- What would make the next year a great year for you?
Do not try to solve anything in this meeting. Write down the answers, thank the person, and tell them when you will come back with a summary.
A one to one template that works every week
A good one to one belongs to the report, not to the manager. Keep a shared running document per person, newest meeting on top, and use the same structure every time so nobody has to think about the format.
| Section | Time | What goes in it |
|---|---|---|
| Their topics | 15 to 20 min | Anything the report added to the doc before the meeting. If the list is empty, ask "what is on your mind this week?" |
| Wins since last time | 3 min | One or two things that went well, named specifically. |
| Blockers | 5 min | What is stuck, and who needs to do what to unstick it. You often own the action here. |
| Feedback both ways | 5 min | One SBI note from you, and one question for them: "what should I do more or less of?" |
| Growth | 2 to 5 min | Progress on their growth goal. Skip this in weeks 1 to 8 until a goal is agreed. |
| Actions | 2 min | Who does what by when. Read them out loud before you close. |
Two rules make this template work. First, never cancel a one to one; move it if you must, but cancelling tells people they rank below everything else on your calendar. Second, start the next meeting by checking last week's actions, including your own.
Feedback with SBI, worked examples
SBI stands for Situation, Behaviour, Impact. You describe when and where something happened, what the person actually did (observable behaviour, not a judgement of character), and what effect it had. Then you stop and listen. The model works because it removes guesswork and labels. "You are not a team player" invites an argument. "In Tuesday's planning meeting, when the estimate came up, you said the front end was not your problem, and the designer stopped contributing for the rest of the meeting" invites a conversation.
Constructive feedback, weak versus strong
| Weak version | SBI version |
|---|---|
| "You need to communicate better with the client." | "In Thursday's call with the client (situation), you agreed to move the deadline without checking with the team (behaviour). Two people worked late on Friday to cover it, and the client now expects that date (impact). What happened from your side?" |
| "Your code reviews are too harsh." | "On the pull request for the billing change yesterday (situation), you left twelve comments and none of them said what was good or which were blocking (behaviour). The author told me she was not sure whether to rewrite everything (impact). Could we agree on marking blocking comments?" |
| "You are always late." | "This week you joined stand-up about ten minutes after the start on three of four days (situation and behaviour). The team repeated updates for you, and the meeting ran over each time (impact). Is something in the mornings making that slot hard?" |
Positive feedback is SBI too
Praise that is vague ("great job") feels nice but teaches nothing. Specific praise tells a person exactly what to repeat. For example: "In the incident review on Monday, you walked through your own mistake first, before anyone asked. That made it easy for the others to be honest too, and we found the real cause in twenty minutes." Aim for roughly three specific positive notes for every constructive one in the first two months, because your team needs to see that you notice good work before they trust your criticism.
The delegation matrix for a new manager
The delegation matrix sorts every recurring task by two questions: how important is it, and how much of your specific skill does it need? Write down everything you did in the last two weeks (a calendar and a task list are enough), then place each item in one of four boxes.
| Needs your specific skill or authority | Someone else can do it well, or learn to | |
|---|---|---|
| High importance | Keep and do. Hiring decisions, performance conversations, setting priorities, managing up. | Delegate with coaching. Leading a project, owning a customer relationship, running the sprint review. Agree check-in points. |
| Lower importance | Schedule or simplify. Reports only you can write, approvals. Batch them into one block a week. | Delegate fully or drop. Meeting notes, routine status updates, recurring small fixes you used to grab. |
A worked example. Priya was promoted to lead a team of six support engineers. Her two week list held 31 items. Eleven landed in "delegate with coaching", including the weekly escalation review she had run for a year. She handed it to a senior engineer, sat in on the first two reviews without speaking, then moved to reading the summary. That one handover gave her back about three hours a week, which went into one to ones she had been rushing.
Delegation fails most often at the handover, not the decision. When you delegate, say what done looks like, what decisions the person can make alone, where they must check with you, and when you will look at progress. Then resist the urge to redo the work. If the result is 80 percent of what you would have produced and the person learned something, that is a good trade in your first quarter.
Common mistakes and what to do instead
- Changing processes in week 2. Wait for the listening summary in week 4. Fix only what is cheap and clearly broken.
- Treating one to ones as status meetings. Move status into a written update and keep the one to one for the person.
- Saving feedback for a formal review. Feedback that waits months becomes a verdict. Give it within a few days, in private.
- Keeping your favourite technical work. Pick at most one area you still own hands-on, and tell the team which one so they know where you will and will not step in.
Where an AI leadership coach fits in
A plan like this is easy to read and hard to keep. Week 6 arrives with a launch, two sick days on the team and an escalation, and the one to one template quietly disappears. This is where an AI leadership coach earns its place. On AiMentoring, Grace, the AI leadership mentor, starts with a goal you write in your own words (for example "become a trusted manager of a six person team within 90 days"), runs a level assessment of 8 to 12 questions and turns the answers into a skill radar across areas such as feedback, delegation, one to ones and managing up.
From there Grace builds monthly milestones and gives you 3 to 5 tasks a week, close to the table above, with a check-in email on Friday during your working hours. You can paste in a draft of a difficult feedback message and get comments against the SBI structure before you send it, or describe a delegation decision and have it checked against the matrix. Every session saves the facts that matter (your team size, the person who is struggling, the change you announced in week 10), so the next conversation picks up where you left off instead of starting from zero. If you miss tasks, the plan is corrected rather than silently abandoned.
Many companies give new managers seats through the Teams plan, which includes manager development tracks and an HR panel that shows only anonymous, aggregated numbers for groups of at least five people, never conversations. If you are buying for yourself, the Personal plan covers one active goal with two mentors of your choice. You can see how the steps connect on how it works, and if you lead a larger programme for many managers, the leadership development platform page explains the company setup, and our comparison of the AI coach for managers options helps when you are choosing a tool.
AI guidance does not replace your judgement or your company's HR policies. For anything involving legal risk, a medical situation or a formal performance process, involve HR. For the everyday work of becoming a good manager, a structured weekly plan with someone checking your progress is the part most new managers are missing.
A short checklist for day 90
- Every report has had at least eight one to ones with you, and each has a written growth goal.
- Each person has received specific positive and constructive feedback, and has given you feedback too.
- Three team priorities are written down, and the team can repeat them without looking.
- You have handed over at least four tasks from your individual contributor days.
- You made one meaningful change based on evidence and reviewed whether it worked.
- Your manager has a written review of the quarter that you both agree on.
If you can tick five of six, your first quarter went well. If you can tick fewer, look at which phase slipped and repeat its weeks in the next quarter. Becoming a manager is not a single promotion event. It is a practice you build one week at a time.