90-Day Plan Template for a New Role (With Example)

A 90-day plan for a new role breaks your first three months into three phases: learn, align, and execute. Each phase has a defined output, so you enter month two with a clear diagnosis and month three with committed priorities and a measurable early win. The template and worked example below give you everything you need to build one and share it before the end of your first week.

Why the first 90 days fail

The failure mode is almost always the same. You arrive with energy, start fixing problems you can see from the surface, and by day 60 you have created resistance among people whose cooperation you need. You have also skipped the problems that were not visible on arrival.

This happens across roles: a new VP of Sales at a growing startup, a product manager moving into a new vertical, a founder stepping up to a general management role for the first time. The tool is the same in each case. The details differ.

A 90-day plan forces you to sequence your work deliberately rather than react to whoever gets to you first.

The three-phase structure

A 90-day plan is not a task list. It is a phased operating model where each month has a distinct purpose and a specific deliverable.

Each phase depends on the previous one. Skip the listening phase and alignment is guesswork. Skip alignment and execution becomes a solo effort the team has not bought into.

Phase 1 (Days 1-30): Listen before you lead

Your only job in the first 30 days is to understand the situation as it actually is, not as you assumed it would be. Resist the urge to propose solutions. Ask questions.

Run structured 1:1s with every direct report, key peer, and major stakeholder. Use the same five questions each time:

1. What is working that I should protect?
2. What is broken that needs fixing?
3. What have we tried that has not worked?
4. What do you wish the last person in this role had done differently?
5. If you could change one thing in the next 90 days, what would it be?

Take notes in the same format every time. You are looking for patterns, contradictions, and things multiple people name independently.

By day 30, write a two-page diagnosis document. Cover: what is working, what is broken, what you are still uncertain about, and your current hypothesis about the highest-leverage problems. You will use pieces of it in phase two.

Phase 2 (Days 31-60): Align on priorities before committing to action

Phase two is about converting your diagnosis into a shared plan. You deliver outcomes through other people; getting alignment before you act is what separates managers who look credible at 90 days from those who look isolated.

Present your diagnosis to your manager or board. Not your solutions yet. Your reading of the situation first. Ask if it matches theirs. Where it does not, find out why. This conversation alone will surface assumptions you did not know you were carrying.

Then set three priorities for the 90-day window. Three only. For each priority, define: the problem you are solving, the metric that tells you it is solved, and the single owner.

This is also when you define your early win. An early win is a specific, visible result that demonstrates you can deliver. It should be achievable within 60-90 days, meaningful to the people who hired you, and low enough risk that a miss does not set you back permanently.

To make your metrics concrete, decide now whether you are tracking progress with OKRs or KPIs. They serve different purposes and mixing them creates confusion. OKRs vs KPIs: What's the Difference and When to Use Each covers when each framework fits.

If you are also working to bring the team behind a new direction, How to Get Team Buy-In on a New Strategy gives a practical framework for that conversation.

Phase 3 (Days 61-90): Execute and generate proof

Phase three is execution, and it is also when you establish your operating cadence. By now, your team should understand how you run meetings, make decisions, escalate issues, and give feedback.

Keep your early win as the priority. Do not let new requests displace it. Your credibility in the next quarter depends on whether you delivered what you committed to in month two.

Track weekly. Look at your three priority metrics every week and be able to say in one sentence whether each one is moving or stuck. If something is stuck by day 75, you do not have time to redesign your approach. Name the blocker and ask for help directly.

By day 90, prepare a short retrospective: what you said you would do, what you actually did, and what you learned. Share it with your manager. This signals that you close loops, and it builds the foundation for your next quarter. For how to structure that next cycle, see How to Run a Quarterly Planning Process for Small Teams.

Template: 90-Day Plan for a New Role

Copy this into a shared document and fill it in within your first week. Revisit and refine it at day 30 and day 60.

---

Name / Role / Start Date:

My mandate in one sentence: [What does success look like at day 90, from your manager's perspective?]

Phase 1: Days 1-30 (Learn)

• Stakeholder 1:1s to complete: [list names and target dates]
• Documents to review: [org chart, strategy doc, board deck, last quarter's results]
• Open questions to answer: [3-5 specific unknowns you need to resolve]
• Diagnosis document due: Day 30

Phase 2: Days 31-60 (Align)

• Diagnosis review with manager: [target date]
• 90-day priorities (three maximum):
  1. Priority: [description] | Metric: [specific measure] | Owner: [name]
  2. Priority: [description] | Metric: [specific measure] | Owner: [name]
  3. Priority: [description] | Metric: [specific measure] | Owner: [name]
• Early win: [what it is, how you will know you have achieved it, target date]
• Team communication: [how and when you will share the plan with your direct reports]

Phase 3: Days 61-90 (Execute)

• Weekly tracking: [how you will review your three metrics each week]
• Early win target date: [specific date]
• Day 90 retrospective: [who receives it, what format]

Risks to this plan: [2-3 things that could derail it, and your contingency for each]

---

Worked example: A new VP of Sales inheriting a struggling team

Marcus joined a 28-person B2B software company as VP of Sales in January. The team had five account executives, $1.4M in ARR, and had missed quota for three consecutive quarters. His mandate: reach $2.1M ARR by year-end, a 50% increase.

Days 1-30. Marcus ran 1:1s with all five reps, both SDRs, the head of marketing, and the CEO. He found that two of the five reps were responsible for 80% of closed revenue, one rep had never received structured coaching, and the CRM was used inconsistently, making pipeline data unreliable. Marketing was generating leads, but sales had never fed back which ones actually converted, so both teams were creating noise for each other.

His diagnosis: the core problem was not effort or market conditions. It was process discipline and a broken sales-to-marketing handoff.

Days 31-60. Marcus presented this to the CEO, who confirmed it matched his own read but said he had not known how to fix it. Marcus set three priorities:

1. CRM hygiene: 100% of active deals logged within 24 hours, achieved by day 60.
2. Lead qualification: a shared definition of a qualified lead, agreed in writing by day 45.
3. Coaching cadence: one structured 30-minute coaching session per rep per week.

His early win: one new enterprise deal closed through the new marketing handoff process, by day 75.

Days 61-90. By day 75, two reps had reached 95% pipeline accuracy. The new lead qualification criteria cut demos from 40 per month to 28, but the close rate on those demos rose from 12% to 19%. Marcus closed a $42,000 enterprise deal that came through a referral triggered by content marketing had been sitting on for months and never promoted through sales.

At day 90, ARR had moved from $1.4M to $1.58M, not the $2.1M target, but the team had a functional process, a coaching rhythm, and a shared pipeline view for the first time in two years. The CEO extended Marcus's trust because he delivered exactly what he had committed to, explained every number, and clearly named the next bottleneck.

The most common mistake: acting before diagnosing

The single most damaging thing you can do in a new role is skip the listening phase because you feel pressure to prove yourself quickly. You arrive with ideas from your last job, start proposing changes by week two, and signal to the team that you are not actually curious about what they already know.

This creates resistance that is disproportionate to what you have actually done. People do not resist change on principle. They resist being changed without being consulted.

The fix is structural: make the listening phase official. Tell your manager that your plan for the first 30 days is to diagnose, not act. Put it in the written 90-day plan so it is visible and deliberate. This reframes the absence of immediate output as a feature of the plan, not a delay.

Once you have earned the right to act, How to Build an Execution Plan That Teams Actually Follow gives a framework for translating priorities into team-level action without losing accountability.

How to present your 90-day plan

Write it down. A plan that exists only in your head is an intention, not a plan. A written plan shared with your manager creates accountability, invites early correction, and signals that you are operating with intention rather than improvising.

Keep it to one or two pages. If you cannot describe your three priorities and your early win in plain language, you have not finished thinking yet.

Present it to your manager at or before the end of week two. The conversation that follows is often more valuable than the document itself. You will find out where your reading of the situation diverges from theirs, and that gap is exactly what you need to close before you commit to phase two.

Key takeaways

• A 90-day plan has three phases: learn, align, execute. Each has a specific output, not just activity.
• Spend the first 30 days diagnosing before proposing. The cost of listening is low; the cost of acting on the wrong diagnosis is high.
• Limit yourself to three priorities for the 90-day window. More than three dilutes focus and makes it easy to avoid accountability when nothing moves.
• Define one early win explicitly: what it is, how you will measure it, and when you will deliver it.
• Share the written plan with your manager before the end of week two. The conversation surfaces misalignments before they become problems.
• At day 90, run a short retrospective and share it. Closing loops builds the trust you will need for every quarter that follows.