90 Day Plan for a New Leadership Role: Template and Example

10 min read ยท 2026-10-25

Here is a 90 day plan for new leadership role holders can use as is: month one is for learning how the organization really works, month two for earning trust with a few visible wins, and month three for committing to a direction that your manager and your team both back. You listen first, decide second, and put the big structural calls after you have evidence.

The plan below covers 13 weeks in six phases, each with a milestone you can check off. It is built for people who lead managers or a whole function: new directors, heads of department, VPs and people promoted into their first senior role. It also covers what generic templates skip: inherited commitments, the questions to ask, how to assess your direct reports fairly, and how to present the plan to your manager or an interview panel.

The roadmap at a glance

Goal: By day 90, you have a written diagnosis, at least two delivered quick wins, a running operating rhythm and a 12-month plan approved by your manager. Duration: 13 weeks (90 days)

  1. Set expectations (Week 1)

    Agree with your manager on what success looks like and tell your team how you will spend the first month.

    • Hold a 60-minute expectations meeting with your manager: top three outcomes for the year, what must not break, and how they want updates.
    • Ask for the list of inherited commitments: dates, hires, budget lines and projects your predecessor promised.
    • Send a short note to your team saying the first month is for listening and that you will not change structure before you have heard from everyone.
    • Book 1:1s with every direct report and a first round of skip-level sessions for weeks 2 to 4.
    • Read the last two quarterly business reviews, the budget, the org chart and the open risk log.

    Milestone: A one-page recap, confirmed by your manager in writing, listing three success criteria for day 90 and how you will report progress.

  2. Listening tour (Weeks 2-4)

    Learn how work really gets done from the people who do it, use it and fund it.

    • Run 45-minute 1:1s with each direct report using the same five questions, so you can compare answers.
    • Hold skip-level sessions in groups of five to eight people, without their managers in the room.
    • Meet each peer leader who depends on your team and ask what they need from you that they do not get today.
    • Join customer calls, escalation reviews or site visits to see the work firsthand.
    • Keep one findings log: theme, who raised it, evidence, and how many times you heard it.

    Milestone: Every direct report, peer leader and key stakeholder met, and a findings log that shows the five themes you heard most.

  3. Diagnose (Weeks 4-6)

    Turn what you heard into a clear read of the situation, the team and the work.

    • Name the situation you walked into: start-up, turnaround, growth, realignment or sustaining success.
    • Assess each direct report on results, potential and fit for the next 12 months, and write down the evidence.
    • Check the numbers behind each theme: backlog, budget burn, attrition, customer complaints or missed dates.
    • Play the findings back to your team in one meeting and ask what you got wrong.

    Milestone: A three-slide diagnosis (what works, what is broken, what is at risk) that your team has seen and corrected.

  4. Quick wins and operating rhythm (Weeks 6-9)

    Show progress on problems people care about and set the routines the team will run on.

    • Pick two or three quick wins from the findings log that are visible, low risk and doable within a month.
    • Give each win an owner from your team, not yourself, and check progress in your weekly staff meeting.
    • Set your cadence: weekly staff meeting, biweekly 1:1s, monthly business review, quarterly planning.
    • Write a one-page decision rights note: what you decide, what your managers decide, and what needs a group call.

    Milestone: At least two quick wins delivered and announced, and the new meeting cadence running for three weeks in a row.

  5. Strategy and people decisions (Weeks 8-11)

    Draft where the team goes next year and the structure and talent it needs to get there.

    • Draft three to five priorities for the next 12 months, each with an outcome and a measure.
    • Test the draft with your direct reports and two peer leaders before it goes up the line.
    • Decide on people moves with HR: open roles, role changes and any performance plans.
    • Prepare the budget or headcount asks the priorities need, and what you would drop if they are refused.

    Milestone: A draft 12-month plan reviewed by your leadership team, with people decisions agreed with your HR partner.

  6. Commit and report (Weeks 12-13)

    Get formal backing for the plan and close the first 90 days with an honest review.

    • Present the plan to your manager and key stakeholders in a 30-minute session built around one summary slide.
    • Run a 90-day review against the three success criteria from week 1.
    • Share the final plan with the whole team and explain what changes for them and when.
    • Set first-quarter goals with owners and put the next review date in the calendar.

    Milestone: Plan approved by your manager, shared with the full team, and first-quarter goals set with a named owner for each.

What makes a leadership 90-day plan different

A first-time manager's plan is mostly about learning the job and the people. When you step into a leadership role, such as director, head of a function or VP, you lead managers, own a budget and sit on a leadership team. Your plan has to serve three audiences at once: the team below you, the peers beside you and the executives above you.

The other difference is the cost of an early mistake. A reorg announced in week three, or a public hint that your predecessor got it wrong, can cost trust that takes a year to rebuild. That is why this plan holds big structural calls until after the diagnosis. Early energy goes into listening, inherited commitments and a few small wins that prove you understand the work.

Your first-week list

The first week sets the tone. Keep it light on opinions and heavy on meetings and reading. This list works for most leadership roles.

Resist the urge to fix things in week one unless something is on fire. If it is, fix it with the team and say clearly that it is an exception, not your new way of working.

  • Expectations meeting with your manager, then a written recap of the three success criteria.
  • Team meeting: who you are, how you like to work, what the first 30 days look like.
  • 1:1s booked with every direct report, plus a skip-level schedule.
  • Access sorted: dashboards, budget files, the HR system, shared drives and the leadership team calendar.
  • Inherited commitments listed: deadlines, promised hires, vendor renewals and open escalations.

Who to meet and what to ask

Use the same short set of questions with everyone. Comparing answers is how you spot patterns, and patterns are more reliable than the loudest opinion in the building.

Ask each person: what is working that I should not touch, what is not working, what would you change first, who else should I talk to, and what do you need from me. The last answer tells you how each person sees your role. Then add the specific topics below for each group.

  • Your manager: success criteria, past disappointments with this team, how they want updates.
  • Direct reports: their goals, their team's biggest blocker, what they expect from you.
  • Skip levels: daily friction, tools that slow them down, what leadership does not see.
  • Peer leaders: handoffs that fail, shared goals, where your team helps or hurts theirs.
  • HR and finance partners: open roles, performance cases, budget rules and the planning calendar.
  • Customers or internal clients: what they rely on your team for and where it falls short.

Example: a new Head of Customer Support's 90 days

Picture an external hire leading a 45-person support team with four team leads, after a year of growing ticket backlog. Here is how the template plays out, phase by phase.

Notice that the quick wins come from the listening tour, not from the leader's previous company. That is why the team accepts them.

  • Week 1: success criteria agreed with the COO: backlog under control, first response time back to target, a plan for next year. Owner: new head of support. Milestone: recap email confirmed.
  • Weeks 2-4: 1:1s with the four team leads, six skip-level groups, meetings with the product, sales and billing leads, two days shadowing agents. Milestone: findings log shows billing tickets and an outdated macro library as top themes.
  • Weeks 4-6: diagnosis shared: a realignment situation, one lead ready for more scope, one lead stretched by a team that is too large. Milestone: team leads correct and approve the diagnosis.
  • Weeks 6-9: quick wins owned by team leads: rebuild the 20 most used macros, and a weekly billing escalation slot with finance. Milestone: both live and announced at the all-hands.
  • Weeks 8-11: priorities drafted: self-service for billing questions, tiered support, a quality review program. Milestone: plan reviewed by the leads and the product director.
  • Weeks 12-13: plan approved by the COO, one new team lead role opened, quarterly goals set. Milestone: plan presented to all 45 agents.

Metrics that show the plan is working

Track two kinds of measures. Business measures show whether the function is getting better. Leadership measures show whether you are building the trust you need to lead change.

Pick the business numbers your manager already watches and baseline them in the first two weeks, so later progress is easy to see. Share the leadership measures with your manager, not with the whole team.

  • Function results: the two or three numbers your manager named, such as delivery dates, pipeline, backlog or budget variance, compared to the week 2 baseline.
  • Listening coverage: how many direct reports, skip levels and peers you have met, tracked in the findings log.
  • Quick wins delivered: how many are live, and which team member owned each one.
  • Team pulse: a short anonymous check at day 30 and day 90 with two questions: do you know the priorities, and do you trust the direction.
  • Regretted departures: people you wanted to keep who resigned during the 90 days.

How to present the plan to your manager or in an interview

For your manager, fit the summary on one slide: the three success criteria from week 1, what you found, three to five priorities, the people and budget decisions you need, and first-quarter goals. Put the evidence in an appendix. Leave out the full findings log and any comments about named people, which belong in a private conversation.

In an interview, you do not know enough to promise results, and pretending you do worries a hiring panel. Present the structure instead: how you will learn, who you will meet, how you will pick early wins and when you will commit to a direction. Add one or two hypotheses from what you learned in earlier interviews, framed as things you would test. Keep it to three to five slides or a single page you can hand over. End with your asks: a leader who knows what support they need comes across as prepared.

How to adapt it to your situation

The template assumes an external hire in a fairly stable organization. Adjust the timing to the situation you walk into.

Whatever the case, keep the same logic: learn, earn trust, commit. Only the length of each part changes.

  • Promoted from within: shorten the listening tour but redo it with new eyes, and reset the relationship with former peers who now report to you in week 1.
  • Turnaround: compress the diagnosis to two or three weeks and make the first decisions sooner, because waiting costs more than an imperfect call.
  • Sustaining success: go slower, since the main risk is breaking what already works.
  • Building a new function: spend more time with peers and on hiring, since there is no team yet to diagnose.

Common mistakes to avoid

  • Announcing a reorg in the first month signals that you judged before you listened, so hold structural changes until your team has seen and corrected the diagnosis.
  • Criticizing your predecessor in public puts loyal team members on the defensive, so talk about what you will build rather than what went wrong.
  • Picking quick wins from your last job leads to fixes nobody asked for, so take them from the top themes in your findings log.
  • Spending all your time with your own team leaves peers and executives unsure of you, so block time every week for peer leaders and your manager.
  • Keeping the plan in your head makes progress invisible, so send your manager a short written update every two weeks against the success criteria.
  • Delaying a hard people decision past day 90 hurts the whole team, so make the call with HR once your evidence is written down.

Frequently asked questions

What should a 90-day plan for a new leadership role include?

It should include success criteria agreed with your manager, a listening tour, a written diagnosis, two or three quick wins, an operating rhythm and a set of 12-month priorities. Each phase needs a milestone you can check. Add the people and budget decisions the plan depends on.

How is a leader's 90-day plan different from a new manager's plan?

A leader plans for three audiences: the team, the peer group and the executives above. The plan also covers managers, budget and structure, so it puts more weight on diagnosis before big decisions. A first-time manager's plan focuses more on learning the work and building 1:1 relationships.

Should I bring a 90-day plan to a leadership interview?

For a senior role, a short plan shows how you think. Keep it to your approach and a few hypotheses, since you do not have the inside facts to promise results. Ask the panel to correct your assumptions, which turns the plan into a conversation.

When should a new leader make changes to the team?

Small fixes can start once you understand the problem, often in the first month. Structural changes and people moves usually come after the diagnosis, around weeks 6 to 10, unless you are leading a turnaround. Make them with HR and with written evidence.

What are good quick wins for a new leader?

Good quick wins are visible, low risk and tied to a problem many people raised in the listening tour. Examples are removing a report nobody reads, fixing a broken handoff with another team, or clearing an old approval backlog. Let a team member own each one so the credit is shared.

Generate this roadmap with AI