90 Day Plan for New Director: Write It, Present It, Get It Approved

Why a director's plan should be a document, not a checklist

A checklist tells you what to do on Monday. A document tells your manager what you think and what you need from them. At director level, approval matters more than activity. Your budget, hiring and structure changes all depend on someone else saying yes.

Treating the plan as a living document also protects you. If priorities shift in week six, you change the document and say why. Without it, a change of direction looks like a lack of direction.

Keep one rule across every version: no more than 2 or 3 goals at a time, each with a number and a date. "Improve reporting" is not a goal. "Cut the monthly close report from five days to three by day 75" is.

The mandate to secure before day one

The mandate is the part most plans skip, and it is the one you will measure yourself against at day 90. Get clear answers to these questions before your start date:

Write the answers on one page and send it back. If your manager edits it, you have learned something important about their priorities before your first meeting.

If the role is new, the mandate is even more important. Nobody has done the job before, so nobody shares a picture of what good looks like. Your one page becomes that picture.

• What three outcomes would make this hire a success after one year?
• What must not break while I learn the role?
• Which decisions can I make alone on budget, hiring and structure?
• Who are the five people whose support I need most?
• Are there known performance issues in the team I should hear about now?
• How often do you want updates, and in what format?

What changes in the diagnosis by function

The versions stay the same. What you diagnose for version 2 and the quick win you propose for version 3 depend on the function you lead.

Choose the quick win on purpose. It should matter to your manager, be finished within 30 days and have a result anyone can check.

• Operations: walk the main process from start to finish and collect delay and error data. A good quick win removes one recurring bottleneck.
• HR: review turnover, open roles and the most frequent employee complaints. A good quick win fixes one broken step in hiring or onboarding.
• Product: review the current roadmap, customer feedback and the delivery rhythm with engineering. A good quick win is a clear prioritization rule the team adopts.
• IT: list open incidents, contracts up for renewal and security risks. A good quick win closes a known risk or clears a slow service request queue.
• Marketing: review channel results, the budget split and how leads pass to sales. A good quick win stops one activity that spends money without results.
• Finance: review the close calendar, forecast accuracy and the requests other teams make most often. A good quick win shortens one report or removes a manual step.

90 day plan for a new director in Word: a one-page layout

Many directors are asked to send the plan as a document. A Word file of one or two pages works well if every version follows the same order. Your manager can then compare versions side by side.

The last section is the one most plans leave out. It saves your manager from rereading the whole document and shows that you adjust the plan on evidence.

• Role and mandate: the three outcomes agreed before day one.
• Stakeholders: names, roles and the week you meet each one.
• Diagnosis: three to five findings, each with its source (a report, a meeting, a number).
• Goals: 2 or 3 goals with a measure and a date.
• Quick win: what it is, its success criterion and its delivery date.
• Decisions needed: budget, approvals or people changes, and who decides.
• Checkpoints: dates of the day 30, 60 and 90 reviews and who attends.
• What changed since the last version: two or three lines.

Presenting the plan to the leadership team

At day 30 or day 60 you may present to a leadership team or committee rather than to your manager alone. Five slides in this order are usually enough:

End with one specific request, such as approving a budget line or a new role by a set date. A committee responds better to a clear question than to a long update. Send the slides a day ahead so the meeting goes to the decision, not the reading.

• What I was asked to achieve: the mandate.
• What I found: three to five points from the diagnosis.
• What I propose: 2 or 3 goals and the quick win.
• What I need: decisions, budget or people, each with a date.
• How we will track it: checkpoints and measures.

The same plan from the HR or hiring manager side

If you are the hiring manager or work in HR, you can prepare most of this plan before the new director arrives. Write the draft mandate yourself and agree it with the director during the offer stage. Gather the documents they will need and share them before day one. Book their first meetings with peers and key clients for the first three weeks. Put the day 30, 60 and 90 reviews in the calendar before the start date.

This turns onboarding into a shared plan rather than a test the new director has to pass alone. It also gives you a fair basis for the reviews, because both sides agreed on the mandate in advance.