30-60-90 Day Plan for a Project Manager: Example, Metrics, Checklist

10 min read ยท 2026-10-25

A 30 60 90 day plan for project manager roles splits your first three months into three goals: understand the projects you inherit by day 30, take ownership of delivery by day 60, and improve how the team plans and reports by day 90. Each stage ends with something your manager can check, such as a project health report or an approved new baseline.

A project manager's first 90 days are not like most jobs. You usually inherit work already in flight, with a schedule someone else built, risks someone else logged and stakeholders who already have opinions. So the plan below starts with a health check of what exists, not a fresh plan. It assumes you join a company that runs several projects at once and that you report to a PMO lead or a head of delivery. Adjust the scope if you run one large program instead.

You will also find a first-week checklist, the people to meet and what to ask them, quick wins that fit the job, the metrics to report, and how to present the plan to your manager or in an interview.

The roadmap at a glance

Goal: By day 90, you run every assigned project with a current baseline, a clean RAID log and a weekly status rhythm that your sponsors and manager trust. Duration: 90 days (13 weeks)

  1. Orient and get access (Days 1-7)

    Get the tools, documents and first conversations in place so you can learn fast.

    • Get access to the project tools (Jira, Microsoft Project, Smartsheet or whatever the team uses), the shared drive and the timesheet or finance system.
    • Read the charter, scope statement, current schedule, last three status reports and the risk log for each project you inherit.
    • Agree with your manager on what success looks like at day 30, 60 and 90, and how often you will check in.
    • Book one-on-ones with each sponsor, the outgoing project manager if there is one, and the leads on each project team.

    Milestone: A list of every project you own, with its sponsor, phase, next milestone date and the documents you have read, shared with your manager.

  2. Learn and assess (Days 8-30)

    Understand where each project really stands before you change anything.

    • Run a health check on each project: scope, schedule, budget, risks, resourcing and stakeholder mood, each rated green, amber or red with a reason.
    • Compare the baseline schedule with actual progress and note every milestone that has slipped or has no owner.
    • Map stakeholders by influence and interest, and note how each one wants to be updated.
    • Sit in on the existing standups, steering committees and vendor calls without changing them yet.
    • Learn the PMO standards: stage gates, templates, change control and reporting deadlines.

    Milestone: A one-page health report per project, reviewed with your manager, with the top three issues and what you plan to do about each.

  3. Take ownership (Days 31-60)

    Run delivery yourself, with schedules and RAID logs that match reality.

    • Re-baseline any schedule that no longer reflects reality, and get the sponsor to approve the new dates in writing.
    • Clean up the RAID log: close stale items, give every open risk an owner and a due date, and add missing dependencies.
    • Set one weekly status report format and a meeting cadence that every team knows.
    • Run the next change request through the formal process so the team sees how scope changes are handled.
    • Chair the next steering committee yourself, with a short list of decisions needed.

    Milestone: Every project has an approved baseline, a RAID log with no unowned risk, and at least two weekly status reports sent on time.

  4. Improve and lead (Days 61-90)

    Fix the delivery problems you found and show results your manager can report upward.

    • Pick one or two process fixes from your health checks, such as a shared dependency board across projects or a clearer handoff to operations.
    • Hold a lessons-learned session on the last milestone delivered and turn the top actions into owned tasks.
    • Coach team leads to update their own tasks so status no longer depends on you chasing people.
    • Track your role metrics for at least four weeks so you can show a trend.
    • Draft your goals for the next quarter.

    Milestone: A 90-day review with your manager showing the metrics trend, the process fixes made and agreed goals for the next quarter.

Your first-week checklist

The first week sets the tone. People will judge you on two things: whether you listen and whether you follow up. Keep your promises small and keep every one of them.

Do not change any process in week one. Even if the status report looks weak, use the current format until you know why it exists. Someone senior may have asked for it that way.

  • Confirm which projects you own and which you only support.
  • Get access to every tool and folder, and chase anything still missing by day 3.
  • Read each project's charter, schedule, budget summary and last status reports.
  • Find the escalation path: who approves scope changes, budget changes and extra people.
  • Introduce yourself in each project channel with a short note on how you will work with the team.
  • Set a weekly 30-minute check-in with your manager.

People to meet in your first 30 days

A project manager rarely has direct authority over the people doing the work. You get things done through relationships, so your meeting list is the real engine of the plan. Meet these people early, ask each of them the same few questions and write down the answers.

Three questions work for almost everyone: what is going well, what worries you most, and how do you want to hear from me. Then compare the answers. When the sponsor and the tech lead name very different main risks, you have found your first priority.

  • Project sponsors: the outcome they expect, what would make them stop the project, and how often they want updates.
  • Your manager or PMO lead: reporting standards, stage gates and which projects leadership watches most closely.
  • The outgoing project manager: open promises, informal agreements and the stakeholders who need extra care.
  • Functional managers: who owns the people on your team and how resource conflicts get settled.
  • Tech lead or lead engineer: where the estimates feel shaky and which dependencies worry them.
  • Finance business partner: how budget is tracked, when forecasts are due and how overruns get approved.
  • Vendor account managers: contract dates, deliverables and the change process written into the contract.

Example: a 30-60-90 plan for a project manager inheriting an ERP rollout

Say you join a manufacturer as project manager for an ERP rollout already in its build phase. The previous project manager has left, go-live is four months away and the steering committee meets every two weeks. Here is how the plan could look, with owners and a milestone for each stage.

Notice that day 30 ends with a recommendation, not just a report. Leadership wants to know whether the go-live date holds. Giving them a clear answer early builds more trust than any process change you could make.

  • Days 1-7 (owner: you): read the charter, the integrator's statement of work and the draft cutover plan. Meet the CFO as sponsor, the integrator's delivery lead and the finance and supply chain leads. Milestone: project list and contact map sent to your manager.
  • Days 8-30 (owners: you and the integrator lead): the health check finds data migration two sprints behind and no owner for test sign-off. Milestone: health report presented at steering, with a recommendation to keep or move go-live.
  • Days 31-60 (owners: you and the sponsor): schedule re-baselined around the data migration fix, a named test manager, RAID log cleaned up. Milestone: new baseline approved by the CFO at steering.
  • Days 61-90 (owners: you and the business leads): cutover runbook drafted, user acceptance testing started, go/no-go criteria agreed. Milestone: first cutover rehearsal booked and the 90-day review held with your manager.

Quick wins that fit a project manager

A good quick win makes the team's week easier and is visible to leadership. Pick wins that come out of your health check, so they solve a real problem and not one you assumed from your last job.

Avoid quick wins that mean a new tool. Moving the team to a new platform in your first month creates work for everyone and gives critics an easy target. Fix the content first. If the tool still hurts after 90 days, raise it then.

  • One status report format for all your projects, sent on the same day each week.
  • A RAID log where every open item has an owner and a date.
  • A shorter standup with a fixed agenda and a parking lot for long topics.
  • A decision log, so steering decisions stop getting reopened.
  • One calendar of milestone dates across your projects, which helps functional managers plan their people.

Metrics to track in your first 90 days

Your manager will judge your first 90 days on delivery and trust. Pick four or five metrics, record a baseline in your first month and report the trend at day 60 and day 90.

Write the definitions down so nobody argues about the numbers in a steering meeting. If your PMO already reports earned value, use its schedule performance index (SPI) and cost performance index (CPI). If not, milestone dates and budget variance are enough.

  • Milestone hit rate: milestones delivered on or before the baselined date, divided by milestones due in the period.
  • Schedule and cost variance: the gap between plan and actual on dates and spend, or SPI and CPI if you use earned value.
  • RAID log health: the number of open risks and issues with no owner or past their due date. Aim for zero.
  • Change request cycle time: days from a change request being raised to a decision.
  • Stakeholder confidence: a short monthly pulse asking each sponsor to rate, from 1 to 5, how clearly they understand project status.
  • Status report timeliness: reports sent on the agreed day, out of the total due.

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

With your manager, present the plan in week one as a draft and ask what you are missing. Use one slide or one page with three columns, one per 30-day stage. Each column holds two or three goals, the main actions and one milestone. Add a row at the bottom for the metrics you will report. Leave out the detailed task list. Your manager wants to see priorities and judgment, not a schedule.

In an interview, the plan shows you think like a project manager before you are hired. Base it on the job description and on what interviewers told you about current projects, and label your assumptions (for example, two projects already in build and a vendor on a fixed contract). Walk through it in two or three minutes. Spend most of the time on days 1-30, because that is where you show you will listen before you change things. End with the metrics you would report at day 90.

Revisit the plan with your manager at day 30 and day 60. Mark what is done, what moved and why. A plan that changes for good reasons shows you are learning.

How to adapt it to your setting

In an agile team, the project manager role often looks like a delivery lead. Swap the baseline schedule for a release plan and a velocity trend, attend sprint reviews and retrospectives in your first 30 days, and agree with the product owner where your role ends and theirs begins.

In an agency or consulting firm, your projects are client work. Add the account manager and the client's project lead to your meeting list, and make contract scope and change orders the first thing you learn. In a regulated industry such as medical devices or banking, spend extra time early on the quality and audit rules for project documents, because a missing sign-off can stop a release.

Common mistakes to avoid

  • Changing processes in your first two weeks makes the team defensive, so observe for a month and change only what your health check shows is broken.
  • Trusting the inherited schedule as it is hides slips you will be blamed for later, so compare it with real progress and re-baseline early with the sponsor.
  • Meeting only the sponsor and your manager leaves you blind to delivery problems, so meet the tech lead, functional managers and vendors in your first month.
  • Promising a go-live date before the health check is done commits you to a guess, so give leadership a date for your recommendation instead.
  • Reporting activity instead of progress loses senior readers, so open every status report with milestones, risks and the decisions you need.
  • Keeping your 90-day plan to yourself means your manager judges you on different goals, so agree on it in week one and review it at day 30 and day 60.

Frequently asked questions

What should a project manager do in the first 30 days?

Learn before you change anything. Read the documents for every project you inherit, meet sponsors and team leads, and run a health check on scope, schedule, budget and risks. End the month with a short health report and priorities agreed with your manager.

How do I write a 30-60-90 day plan for a project manager interview?

Use the job description and what you learned in earlier interview rounds. Keep it to one page with three columns: learn, take ownership, improve. Label your assumptions and finish with the metrics you would report at day 90.

What metrics should a new project manager report?

Milestone hit rate, schedule and cost variance, RAID log health, change request cycle time and stakeholder confidence make a solid set. Record a baseline in your first month so you can show a trend at day 60 and day 90.

How is a project manager plan different from a program manager plan?

A project manager plan focuses on getting individual projects under control: schedules, RAID logs and status reports. A program manager plan spends more time on benefits, dependencies between projects and governance across the program. The 30-60-90 structure stays the same.

What if I inherit a project that is already failing?

Speed up the health check and take it to the sponsor within two weeks instead of 30 days. Explain what you found, the options and what you recommend. Then reset the baseline or the scope with the sponsor's written approval.

Generate this roadmap with AI