A 90-day plan for a first-time manager is a structured sequence of learning, relationship-building, and lightweight process-setting that gives you a foundation to manage from, rather than improvising.
The common failure mode is treating the first 90 days as a performance. New managers try to demonstrate leadership by acting decisively, reorganizing things, and being visibly helpful. The result is a team that is impressed but does not trust them with problems yet. The goal is not to impress the team. It is to understand it well enough to make good decisions.
Key takeaways
- The first month is for understanding the work, the people, and the context.
- The second month is for building habits: regular 1:1s, a clear prioritization system, and a way to track commitments.
- The third month is for identifying one concrete problem to solve and solving it visibly.
- Document every 1:1. Notes from the first 90 days are the baseline you will use for performance reviews later.
Why it matters
First-time managers often have no model for what the job actually is. They know what managing looked like from below, but that view is incomplete. From below, you see the outputs of management: decisions, feedback, structure. You do not see the inputs: the time spent understanding context, the difficult conversations, the work of keeping alignment between the team's work and the organization's priorities.
The 90-day frame matters because it gives you permission to be in learning mode instead of action mode. If you have set expectations correctly with your manager, you are not expected to have fixed anything by day 30. You are expected to understand the terrain. This permission is real and worth using.
The habits you set in the first 90 days will define how you manage for years. If you start skipping 1:1s in week three because you are busy, you will skip them whenever things get hard. If you start documenting decisions in a shared place from day one, that habit will save you when you need to revisit a choice six months later.
How it works in practice
A 90-day sequence for a first-time engineering manager
-
Days 1 to 30: understand the work
Schedule 1:1s with every direct report and with your own manager. Ask each report: 'What is the most important thing I should understand about the work? What is the biggest thing slowing you down?' Read the backlog, the recent retros, and any open technical decisions. Take notes on everything. Do not act on any of it yet.
-
Days 1 to 30: understand the people
Ask each person: 'What kind of feedback do you want from me and how often? What does a good week look like for you? What would make you feel like this team is going well?' You are learning how each person works, not evaluating them yet.
-
Days 31 to 60: build the recurring rhythm
Set a fixed 1:1 schedule for every direct report (30 to 45 minutes, weekly or biweekly). Set up a shared notes doc for each 1:1. Start tracking your own commitments in a simple list and review it every Monday morning.
-
Days 31 to 60: practice the basics
Write feedback to yourself after every 1:1 (not to them yet). Practice naming what you observed: 'In the sprint review, I noticed X. I want to ask about it.' Hold the 1:1 agenda to three items or fewer. Ask more than you tell.
-
Days 61 to 90: pick one problem and solve it
By week eight you should have a clear picture of one recurring problem the team has that is in your power to fix. Name it to the team, describe your plan, fix it, and follow up to confirm it is fixed. This is your credibility moment, not a sweeping reorganization.
Common mistakes
Trying to be liked before being trusted
Likeability does not help you when you need to give hard feedback or make a call the team disagrees with. Be direct from day one.
Not asking your manager what success looks like at 30, 60, and 90 days
You cannot calibrate your performance against standards you do not know. Ask in week one.
Running 1:1s without notes or follow-through
A 1:1 with no notes is a conversation. A 1:1 with notes and follow-through is a management relationship. The difference compounds over time.
Avoiding the first hard conversation
There will be one. A missed deadline, a conflict, a piece of poor work. Delaying it teaches the team that you will not address things directly. Early directness sets a standard that makes everything easier later.
What it sounds like
Guy is in his fourth week as a first-time manager, reviewing his notes from his initial 1:1s with his team.
Daniel: “So I have been looking at my notes from the first round of 1:1s. Three different people mentioned that sprint planning runs too long and nobody feels like priorities are clear coming out of it.”
Merav: “Yeah, we usually spend 40 minutes debating scope and then just add everything to the sprint anyway.”
Guy: “Okay. I am going to try a different format next sprint. 20 minutes max, with the top five items ranked before we walk in. If it does not help, we will try something else.”
Questions managers actually ask
What if I inherited a team and am also a first-time manager? Where do I start?
Run the listening tour from the managing an inherited team playbook inside the 90-day frame. The two are compatible. Listening comes first either way.
How do I handle it when my reports ask me to make calls I am not sure about yet?
Say: 'I need 24 hours to think about this and look at the context. I will give you an answer tomorrow.' Decisive does not mean instant. It means you actually decide.
Should I change anything in the first 30 days?
Only if something is actively broken and the cost of waiting is real. Otherwise, the discipline is to understand before you act.
How do I manage someone older or more experienced than me?
Acknowledge the dynamic directly: 'You have more experience with this codebase than I do. I am going to rely on your judgment on technical decisions. What I am responsible for is prioritization and removing blockers.' Then do exactly that.
What do I document and where?
Keep a private notes doc per person with dates. Note what was discussed, what you committed to, what they committed to, and your observations. This is your record, not a performance file.
What is the one mistake that sets new managers back the most?
Avoiding the first hard conversation. Every week you wait to address a problem, you are teaching the team that problems do not get addressed.
See how Leap improves execution in your meetings
Leap sits in your meetings, captures decisions and owners in real time, and shows you where execution breaks down before the week is out.