You find out on a Friday. By Monday you are a manager.
Maybe you were the strongest individual contributor on the team and leadership decided to promote you. Maybe you were hired from outside to run a department you’ve never worked in. Maybe there was a reorg, someone left, and the team landed in your lap with three days of notice.
Three very different situations. Three very different starting points. But the question is the same: what do you actually do in the first 90 days?
Most advice stops at “build relationships” and “set clear goals.” That is not a plan. That is a sentence. What you need is a week-by-week structure that tells you when to listen, when to act, and when to have the conversation you’ve been putting off.
That’s what this post is.
Why the First 90 Days Matter More Than You Think
Michael Watkins, in his research on leadership transitions, found that leaders who fail in new roles almost always make the same mistake: they act before they understand. They bring solutions from their last job. They make changes before they’ve earned the standing to make them. And by the time they realize it, the trust is already gone.
The foundation of a strong first 90 days is knowing which essential new manager skills to develop first — before you’re deep in the role and reacting to problems.
Your team is forming an opinion of you before you’ve said a single word in a meeting. They watch how you handle the first awkward silence. They notice whether you remember their names after the first introduction. They register whether you asked about their work or just talked about yours.
The first 30 days set your trust baseline. The signals you send in days 1-14 are remarkably hard to reverse. A manager who swoops in with a reorganization plan in week two will spend the next six months fighting a credibility deficit that could have been avoided entirely.
The good news: most of this is preventable if you know what phase you’re in.
Days 1-30: Listen and Learn
Your only job in the first 30 days is to understand. Not fix. Not optimize. Not prove you were the right hire. Understand.
Week 1: Introductions and orientation
Meet everyone. Not in a “town hall” format where you talk for 20 minutes. Individually, or in pairs, with enough time to actually hear them. Set up your 1:1 cadence. Get your calendar under control. Figure out what meetings are actually useful versus the ones that exist out of inertia.
The most important rule for week one: do not change anything. Not even the thing that is obviously broken. Especially not that. You do not understand why it’s broken yet, and you do not know who built it or why they built it that way.
Week 2: Shadow and map
Sit in on the work. Attend the standups, the planning sessions, the customer calls. You’re not there to run them. You’re there to watch how the team actually operates versus how it’s supposed to operate on paper.
Start mapping your stakeholders. Who does your team depend on? Who depends on your team? Who has opinions about how this function should run? You’ll need that map later when you’re trying to get anything done.
You will probably spot two or three things you could fix quickly. Write them down. Do not act on them yet.
Week 3: The deep 1:1s
This is the most important week of your first month. Schedule 45-60 minutes with each of your direct reports. These are not status updates. These are listening sessions. Use the five questions (covered below).
Active listening is the skill that determines whether this week produces real signal or polished answers. Most people will tell you what they think you want to hear unless you create enough space for something more honest.
Week 4: Synthesize
Take everything you’ve heard and start to make sense of it. Where do people agree? Where do they disagree? What are the recurring themes? What are the things nobody is saying out loud but that keep showing up sideways?
By the end of week four, you should be able to write a one-page thesis on the state of the team: what’s working, what’s not, and what the biggest opportunities are. You’ll share this in week five.
What to avoid in days 1-30: making changes before you understand the context behind them, holding opinions you formed before you started, and mistaking confidence for competence.
Days 31-60: Diagnose and Align
You’ve listened. Now you start to move. But deliberately, not frantically.
Week 5: Share your thesis
Bring your observations to your manager. Not as a complaint list. As a synthesized point of view: “This is what I’m seeing. This is what I think it means. This is what I’m considering. What am I missing?”
This conversation serves two purposes. It gives you a reality check before you commit to a direction. And it starts building the management relationship you’ll need when things get complicated later.
Week 6: Lock in your priorities
Based on your week-five conversation, pick two or three things to focus on in the next 30 days. Not ten. Not five. Two or three. The discipline of choosing is part of the job.
Each priority should be specific enough that someone could tell you, at the end of 30 days, whether you achieved it.
Week 7: Tell the team
Communicate your priorities to your direct reports. Be clear about what you’re focusing on and why. Be honest about what you’re not going to focus on right now and why that’s also a deliberate choice.
Teams find this steadying. Most people have worked for managers who chased every shiny object. Being told “we are doing these three things and not the other seven” is often a relief.
Week 8: The conversation you’ve been putting off
By week eight, you know what it is. There’s a performance issue you’ve been documenting. A dynamic between two team members that’s dragging the whole team down. A process that everyone knows is broken and nobody has fixed because the previous manager avoided the conversation.
Have it. Week eight is late enough that you’ve earned the credibility to have it. It’s early enough that you haven’t let the problem compound for another month.
Constructive feedback is the skill most new managers underinvest in because it feels risky. It is risky to avoid it.
Days 61-90: Execute and Lead
You’ve listened. You’ve diagnosed. Now you lead.
Week 9: First measurable deliverable
Your team should ship something, finish something, or demonstrate measurable progress on one of your three priorities. This matters for two reasons. It proves the priorities were real, not rhetoric. And it gives the team a small win to build on.
Be visible about it. Acknowledge the work. Connect it to where you’re all going.
Week 10: Check in on yourself
Ask your manager for a mid-point check. Not a performance review. A genuine “how am I doing from your vantage point” conversation. What are you doing well? What would they do differently in your position?
Most new managers wait until the formal review cycle for this feedback. That’s 90 days of avoidable drift.
Week 11: Skip-levels
Have one-on-ones with people who report to your direct reports. The goal is not to undermine your reports. It’s to understand how your team’s work connects to the people actually doing it, and to demonstrate that you’re accessible.
Do this once. Tell your direct reports you’re doing it and why.
Week 12: The 90-day review
Sit down with your manager and close the loop. What did you set out to do in 90 days? What did you accomplish? What surprised you? What are you carrying into Q2?
This conversation should include a set of goals for the next quarter. Not a continuation of onboarding. You’re past that now.
Goal-setting at this stage is about committing to outcomes you’re accountable for, not aspirations you hope will happen.
The 5 Questions Every New Manager Should Ask in 1:1s
These are for the week-three deep 1:1s. They work across roles, industries, and team sizes. Write them down. Use them exactly.
1. What’s working for you right now?
Start with what’s good. It tells you what to protect. It also tells you what the person values, which is more useful than their job description.
2. What’s broken and nobody’s fixing?
This is the question that surfaces the real problems. “Nobody’s fixing it” is the key phrase. It signals the person has already given up hope that it will change on its own. You want that list.
3. What do you wish the last manager had done differently?
This takes some trust to answer honestly, and not everyone will. But the people who do will give you the clearest picture of what this team actually needs from its leader.
4. What are you working on that I should understand?
This signals that you see them as more than a task list. It also catches the things that never make it into status updates, the side projects, the cross-functional work, the thing they’re almost done with that nobody else knows about.
5. What do you need from me in the first 90 days?
The most important question and the most underused one. People will tell you if you ask. They rarely volunteer it.
The Common 90-Day Mistakes
Making changes in the first two weeks. You do not understand the system yet. Even correct changes made too early erode trust, because they signal that you weren’t really listening.
Not asking enough questions in week one. Curiosity signals intelligence, not inexperience. The managers who talk too much in week one are the ones who run out of goodwill by week six.
Delaying the hard conversation past day 60. If you wait until month three to address the thing everyone knows about, you’ve told the team two things: that you saw it and did nothing, and that you’ll probably keep doing nothing. Both are damaging.
Setting too many priorities. Everything urgent is not a priority. If you name eight priorities, you’ve named zero priorities. The discipline of focus is one of the hardest things to practice in a new role when everything feels important.
Forgetting to check in on your own state. New managers often operate in performance mode for the full 90 days without pausing to assess how they’re doing. By day 75, they’re either burned out or coasting. Neither is a good setup for quarter two.
Three Scenarios, Different Plans
Promoted from within the team
You know the work. That’s an asset. But you also have pre-existing relationships, and some of them are now managerial relationships. That shift is harder than it sounds. Your former peers will test whether you play favorites. The people who were passed over for your role are watching you closely.
Spend more time in weeks one and two being explicit about how your role has changed. Don’t pretend the dynamic didn’t shift. Address it directly in your 1:1s.
Brought in from outside
You have no pre-existing credibility on this team. Everything you know about leadership has to be rebuilt in this context, with these people. The temptation to solve problems fast with knowledge from your previous role is strong and usually a mistake.
Stay in listen mode longer. Week three for the deep 1:1s might extend into week four. That’s fine. The cost of being slower is lower than the cost of being wrong.
Inherited after a reorg
This is the hardest scenario. The team didn’t choose this transition. They may have lost a manager they trusted. There may be unresolved emotions about the reorg itself that have nothing to do with you.
In week one, acknowledge it. You do not have to have all the answers. Saying “I know this transition wasn’t easy and I’m going to take the time to understand where everyone is” is more valuable than any 90-day plan you could present on day one.
For all three scenarios, the solutions for new managers at Risely covers the specific challenges that show up in the first three months.
Your Between-Phase Reflection Tool
The 30-60-90 plan works best when you’re pausing to reflect, not just executing tasks. At the end of each phase, take 30 minutes with Merlin to process what you learned, what surprised you, and what you want to carry into the next phase.
Try Merlin free and use the between-phase check-ins to sharpen your leadership instincts as you go, not after you’ve already made the call.
Frequently Asked Questions
What is a 30-60-90 day plan for a new manager?
A 30-60-90 day plan is a phased framework that structures your first three months as a manager. The first 30 days focus on listening and learning. Days 31-60 are about diagnosing what’s actually happening and aligning on priorities. Days 61-90 shift to execution and accountability. The value is in the phasing: most new managers try to do all three at once and end up doing none well.
What should a new manager do in the first 30 days?
In the first 30 days, a new manager should focus entirely on understanding, not fixing. That means individual 1:1s with every direct report, shadowing the actual work, mapping stakeholders, and resisting the urge to make changes before understanding what’s behind them. The five-question 1:1 framework in this post is a good structure for those early conversations.
What are the biggest mistakes new managers make in the first 90 days?
The most common mistakes are making changes before earning enough context, delaying difficult conversations until they’ve compounded, naming too many priorities, and failing to check in on their own performance mid-way through. The mistake that does the most damage fastest is acting before listening.
How does the 30-60-90 day plan change based on how you got the role?
If you were promoted from within, pay extra attention to the relationship shifts with former peers. If you came in from outside, extend the listening phase and resist importing solutions from your previous context. If you inherited a team after a reorg, acknowledge the disruption directly and explicitly. The weekly structure stays the same. How you show up in each week varies.
Should a new manager set goals in the first 30 days?
Set goals for yourself as a learner in the first 30 days, but not operational goals for the team. You don’t have enough information yet to set meaningful team goals. The time to commit to team priorities is weeks five through seven, after your listening phase is complete and you’ve pressure-tested your observations with your manager.
How does Merlin help with the 30-60-90 day transition?
Merlin is Risely’s AI coach. It’s most useful at the reflection points: the end of phase one, before your week-five conversation with your manager, and before the week-twelve review. You can use it to process what you’ve observed, stress-test your thinking, and prepare for conversations that require nuance. It’s available inside Slack and Microsoft Teams so it fits into where the actual work happens.