30-60-90 day plan for new managers

A 30-60-90 day plan for a new manager fails when it is written like an individual contributor's plan with "manage the team" bolted on. The real milestones for someone new to managing a team — whether promoted from inside or hired from outside — are about understanding the people and the work well enough to make one good decision by day 90, not about personal output.

Below is a plan built around one-on-ones, a written diagnosis of the team, and a first owned decision, with what the new manager's own manager owes at each phase. For the general new-hire version of this template, see the 30-60-90 day plan template for new hires.

What is different about a first 90 days in management

An individual contributor's first 90 days are judged by what they personally produced. A manager's are judged by whether the team's work is in better shape than they found it, which is a much harder thing to see quickly. The plan below solves that by making the early phases about diagnosis — understanding the team, the work and the constraints — before asking for any change the manager will be judged on. A manager who tries to prove themselves by changing things in week two, before they understand why things are the way they are, usually breaks something that was working for a reason nobody told them about.

The 30-60-90 day plan

30-60-90 day plan — [Name], manager of [team], reporting to [manager's name]
Start date: [date]        Team size: [N] direct reports        Prior state: [promoted internally / hired externally]

DAYS 1-30 — Listen and diagnose. No structural changes.
Owns:
- A first one-on-one with every direct report within the first two weeks
- A written map of the team: who does what, current priorities, known blockers
- Sitting in on at least [N] pieces of the team's actual work (code review, sales calls,
  patient rounds, campaign reviews — whatever the team does) to see it firsthand
- A list of decisions inherited from the previous manager that are on hold, with dates
Produces by day 30:
- A one-page team diagnosis: strengths, risks, and the two or three things worth changing
- A one-on-one cadence set with every report (day, time, length) and kept for 30 days straight
Manager's manager owes:
- Context on why the team is structured the way it is, and what not to touch yet
- Introductions to the peers and stakeholders the new manager will need
- An explicit "no major changes expected yet" so the new manager is not guessing

DAYS 31-60 — Make the first calls, with the manager's manager as a sounding board
Owns:
- Act on one or two items from the day-30 diagnosis, chosen with the manager's manager
- Give one direct report structured, specific feedback on real work, not "you're doing great"
- Run the team's regular meeting (standup, pipeline review, huddle) solo
- Flag one performance or capacity concern in the team, if one exists, rather than waiting
Produces by day 60:
- Evidence of at least one improvement the team can point to (a removed blocker, a fixed process)
- Notes from every one-on-one so far, showing patterns across the team, not just individuals
Manager's manager owes:
- A monthly skip-level with the team, shared back with the new manager afterward
- Real-time coaching before a hard conversation, not just a debrief after it
- Cover for one decision the new manager gets wrong, so they keep making decisions

DAYS 61-90 — Own the team's next quarter
Owns:
- Propose the team's goals or priorities for the next quarter, not just execute a list handed down
- Complete a first round of informal check-ins framed around each report's own goals
- Make one staffing or workload call independently (reassign work, flag a hire, address underperformance)
Produces by day 90:
- A written 90-day self-assessment against this plan
- A next-quarter plan for the team, presented to the manager's manager for a decision, not approval-seeking
Manager's manager owes:
- The 90-day review, calendar-blocked from day one
- A clear answer on what decision rights the new manager has going into the next quarter

Review cadence: weekly one-on-one between the new manager and their manager throughout;
formal check-ins at day 30, 60 and 90; one skip-level with the team by day 60.

A filled example: an invented operations team lead

The one-on-one cadence that anchors the whole plan

Every phase above depends on one-on-ones actually happening on schedule, because they are where a new manager learns what the team diagnosis needs to say and where problems surface before they become incidents. Set the cadence in week one — same day, same time, every week, even if there is nothing urgent to discuss — because a one-on-one that gets cancelled twice in the first month tells the team it is optional, and the manager loses the channel exactly when they need it most to understand what is really going on.

Keep short written notes after each one, not for surveillance but so patterns across the team become visible: three people separately mentioning the same blocker in week three is a diagnosis finding, and it only shows up if someone wrote each mention down.

What the new manager's own manager owes

How the 90-day review should run

Structure the day-90 conversation around the team's outcomes, not a personal performance rating. Walk through the diagnosis written at day 30, check which items were addressed and which were deliberately left for later, and read the one-on-one notes together for patterns the new manager might have missed. End with the decision rights question explicitly: what can this manager decide alone starting day 91, and what still needs a check-in. Leaving that unstated is the single most common reason new managers either overreach or under-decide in their second quarter.

Common mistakes in a new manager's first 90 days

The most common failure is treating the first 30 days as downtime instead of diagnosis time, because nothing visible is being produced. A new manager who spends those weeks in genuine one-on-ones and firsthand observation of the work is not behind; they are building the map every later decision depends on. The second most common failure is the opposite: changing something structural in week two to establish authority, before understanding what problem it was solving. Both come from the same discomfort with not yet having anything to show, and both are fixed by writing the diagnosis down and sharing it, so "not producing yet" becomes visibly "producing the plan for what comes next."

Adapting the plan by starting point

• Promoted from inside the team: compress the observation phase, since the work is already known, but do not skip the relationship reset with former peers, and expect the first hard feedback conversation to be harder emotionally than the template suggests.
• Hired from outside: extend the diagnosis phase to a full 30 days even under pressure to show quick wins; an outsider's early "improvement" is often a fix for a problem that does not exist.
• Managing a team larger than 8: add a skip-level layer to the one-on-one cadence (team leads first, their reports through them) so the diagnosis phase does not consume all 30 days in scheduling alone.
• Managing a team through a reorganization: add an explicit day-30 goal of stating what is not changing, since uncertainty during a reorg does more damage to trust than almost any single decision would.