30 60 90 Day Plan for a Director: Example, Priorities and Metrics

11 min read · 2026-10-25

A 30 60 90 day plan for director roles lays out what you will learn, decide and deliver in your first three months as the leader of a function. For a director, the plan is less about your own output and more about three things: understanding the business and the team you inherit, setting a direction your managers can carry out, and earning the trust of your VP and your peers in other functions.

The plan below covers 13 weeks in five phases, from your first conversations to a 90-day review with your manager. Each phase has concrete steps and a milestone you can check. You will also find a first-week checklist, the people to meet in order, quick wins that suit a director, the metrics your boss will look at, and how to present the plan in a final-round interview or in your first week.

It works for any function: engineering, product, marketing, sales, operations, finance or HR. The example follows a director of customer support, so you can see what each phase looks like with real names on it.

The roadmap at a glance

Goal: By day 90, you have assessed your team and budget, your VP has approved a written strategy and quarterly plan, two quick wins are delivered, and a monthly metrics review is running. Duration: 13 weeks (90 days)

1. Listen and map the landscape (Weeks 1-2)

   Learn what your VP, your managers and your peers expect before you change anything.

   • Agree with your VP on what success looks like at day 90, the two business problems they most want solved, and how they want to be updated.
   • Hold a one-on-one with every direct report using the same five questions, and keep notes you can compare later.
   • Read the last two quarterly business reviews, the current budget, the headcount plan and any open customer escalations.
   • Meet the peer directors whose teams depend on yours and ask what they need that they are not getting.
   • Tell the team how the first month will work: mostly listening, no reorganization, urgent decisions still get made.

   Milestone: Every direct report and key peer met, and your VP's day-90 success criteria written down and confirmed by email.

2. Assess the team, the work and the money (Weeks 3-4)

   Build an honest picture of your people, your projects and your budget.

   • Run skip-level meetings with small groups of individual contributors to hear what may not reach you through managers.
   • Privately rate each manager on performance and potential, and note the support each one needs.
   • Map the budget with your finance partner: committed spend, open headcount, vendor renewals and where the forecast is at risk.
   • List every active project with owner, status and business value, and flag the ones nobody can explain.
   • Write a two-page day-30 memo: what works, what does not, and the questions you still need to answer.

   Milestone: Day-30 memo reviewed with your VP, with agreement on the problems your strategy must address.

3. Form a point of view (Weeks 5-8)

   Turn what you learned into a strategy your managers helped write.

   • Draft a one-page strategy: where the function should be in 12 months, three priorities that get it there, and what you will stop doing.
   • Test the draft with your managers in a working session and let them change it before anyone outside the team sees it.
   • Walk peer directors through the parts that affect them and settle conflicts on timing or shared resources.
   • Deliver a first quick win that your team can finish alone within four weeks.
   • Choose the five to seven metrics you will report and pull a baseline for each one.

   Milestone: Strategy approved by your VP, first quick win delivered, and a baseline recorded for every metric.

4. Make the hard calls and launch the plan (Weeks 9-11)

   Act on people, structure and priorities so the strategy can actually run.

   • Make the people decisions you have been weighing, such as a performance plan, a promotion, a role change or a new hire.
   • Change the team structure only if the strategy needs it, and explain the reason to everyone in one meeting.
   • Turn the three priorities into a quarterly plan with an owner, a milestone and a date for each.
   • Pause or cut projects that do not serve the priorities, and tell their sponsors yourself.
   • Present the strategy at a team all-hands and answer questions in the open.

   Milestone: Quarterly plan published with a named manager owning each priority, and every paused project communicated to its sponsor.

5. Set the operating rhythm and review (Weeks 12-13)

   Install the routines that keep the function on track after the first 90 days.

   • Start a weekly staff meeting with a fixed agenda: metrics, decisions needed, risks.
   • Set up a monthly business review with your VP that uses the same metric pack every time.
   • Prepare your budget and headcount request for the next planning cycle, tied to the strategy.
   • Ask your VP, two peers and your managers for direct feedback on your first 90 days.
   • Run a 90-day review: what you found, what you changed, early results and the plan for the next two quarters.

   Milestone: 90-day review held with your VP, feedback collected, and the next two quarters of the plan agreed.

Common mistakes to avoid

• Reorganizing in the first month breaks trust before you understand the work, so hold structural changes until your assessment is done and you can explain the reason.
• Spending all your time with your own team leaves peers guessing, so meet your peer directors in the first two weeks and keep a recurring slot with the two you depend on most.
• Judging managers on first impressions leads to wrong calls, so rate them only after skip-levels, project reviews and at least two one-on-ones each.
• Picking a quick win that needs another team's approval stalls it, so choose one your team can deliver alone within four weeks.
• Presenting a strategy your managers did not shape gets polite nods and slow execution, so write it with them before it goes to your VP.
• Going quiet with your VP for 90 days risks drifting from what they need, so send a short written update every two weeks on what you learned and what you decided.

Frequently asked questions

What should a director include in a 30 60 90 day plan?

Include a goal for each 30-day block, the people you will meet, how you will assess the team and the budget, one or two quick wins, the metrics you will report and a date for your strategy. Close with a 90-day review with your manager. Keep it to one page so it is easy to update.

How is a director's 30-60-90 day plan different from a manager's?

A manager's plan focuses on one team and their own delivery. A director's plan covers several teams led by managers, a budget, peer relationships across functions and a strategy for the whole area. It also includes people and structure decisions, which most manager plans do not.

How do I present a 30-60-90 day plan in a director interview?

Use one page with three columns, each with a goal, a few actions and a success measure. Spend most of your time on how you will learn and who you will meet, then share one or two ideas you would test. State your assumptions and ask what would change them.

When should a new director make changes to the team?

A common approach is to wait until you have met everyone, run skip-levels and reviewed the work, which often takes four to eight weeks. Urgent problems, like a failing launch, should be handled right away. Structural changes should follow the strategy, not come before it.

What are good quick wins for a new director?

Good quick wins are visible, owned by your team and done within a few weeks: clearing stuck approvals, fixing a handoff with a peer team, cancelling a report nobody reads or filling a long-open role. Pick from problems several people raised in your first conversations.

Generate this roadmap with AI