30-60-90 Day Plan for a Project Manager (with Example and Free Template)

A 30-60-90 day plan for a project manager splits your first three months into three phases. In days 1 to 30 you learn: meet stakeholders, understand why the project exists and get an honest view of its health. In days 31 to 60 you own: take over governance and reporting, agree a realistic plan and get risks under control. In days 61 to 90 you improve: remove recurring blockers, grow the team and show results in a 90-day review. Each phase has three to five goals, and each goal has an output and a way to know it's done.

I'm Gulab Chand Tejwani, PMP and Microsoft Certified Trainer at TechNet Consultancy in Anand, Gujarat. Whether you're interviewing for a project manager role or starting one next week, this is the plan I'd write. There's a worked example below and a free Excel template you can fill in.

What is a 30-60-90 day plan?

It's a short written plan for your first 90 days in a new role, broken into three 30-day phases with clear goals for each. Managers ask for one in interviews because it shows how you think: whether you listen before acting, whether you understand that a project has a sponsor, a team and a set of risks, and whether you can turn that into concrete actions. Once you start the job, the same plan keeps you focused when everything feels urgent.

Days 1-30: what should a new project manager do first?

Learn before you change anything. The fastest way to lose a team's trust is to arrive with fixes for problems you don't yet understand.

• Understand why the project exists. Read the business case, charter and contract. Ask the sponsor what success looks like for them.
• Meet the key stakeholders. Hold 1:1s with the sponsor, product owner, team leads and client contact. Ask what's working, what isn't and what they need from you.
• Get an honest view of project health. Review the schedule, budget, risk and issue log and recent status reports, then compare them with what people told you.
• Understand the team. Attend each meeting once without changing it. Meet each team member individually.
• Earn trust with one quick win. Fix a small, visible irritant the team raised.

By day 30 you should be able to state the project's goal, its top risks and its real status, and the sponsor should agree with you.

Days 31-60: how do you take ownership?

Now you run the project rather than observe it.

• Take over governance and reporting. Chair the status meetings, keep the risk and issue log current, and send the status report yourself.
• Agree a realistic plan. Where the health check showed gaps, re-plan with the team. Put baseline or scope changes through change control rather than quietly absorbing them.
• Get risks under control. Review the top risks, give each an owner and agree a response.
• Set up communication that works. Agree who needs what information, how often and in what format.

Days 61-90: how do you show impact?

• Remove a recurring blocker. Use retrospective findings to fix the one thing that slows the team most often.
• Grow the team's capability. Clarify roles, delegate decisions the team can own and coach where skills are thin.
• Present a 90-day review. Show what you found, what you changed, results against the plan and your priorities for the next quarter.

Example: a 30-60-90 day plan for a new IT project manager

Phase	Goal	Done when
Days 1-30	Understand why the project exists	You can state the goal and top three success measures, and the sponsor agrees
Days 1-30	Meet the key stakeholders	Every key stakeholder met once; stakeholder register drafted
Days 1-30	Health check	Sponsor and team agree with your view of schedule, cost, scope and risk
Days 31-60	Own governance and reporting	Weekly status reports go out on time, with no surprises
Days 31-60	Agree a realistic plan	Sponsor signs off the updated plan or backlog
Days 31-60	Take charge of risks	Every top risk has an owner and a response
Days 61-90	Remove a recurring blocker	That blocker stops recurring
Days 61-90	90-day review	Sponsor agrees next-quarter priorities

The template has this example in full, with key actions, outputs, owners and due dates, plus a blank sheet for your own plan.

How do you present a 30-60-90 day plan in an interview?

Keep it to one page or three slides, one per phase. For each phase, show three to five goals and how you'll measure them. Say plainly that the first 30 days are about listening, then name the kinds of things you expect to find, such as unclear priorities or an out-of-date risk log, without claiming you already know the answers. Interviewers want to see judgement and structure, not a promise to transform everything in a month.

What mistakes should you avoid?

• Changing things in week one. You don't yet know why things are the way they are.
• Goals without measures. "Improve communication" isn't a goal; "stakeholders confirm they get what they need" is.
• Ignoring the sponsor. If the sponsor doesn't agree with your plan, it isn't the plan.
• Writing it and forgetting it. Review it every two weeks and update the status of each goal.

Building your project management skills

A 30-60-90 plan uses the same thinking the PMP exam tests: understand before acting, engage stakeholders, manage risk and change deliberately. If you're thinking about certification, read is PMP worth it in 2026 and our step-by-step guide to preparing for the PMP exam.

Test your project judgement. Take a free PMP mock test in your browser →

FAQ

What is a 30-60-90 day plan for a project manager?

A plan for your first 90 days, split into three 30-day phases: learn (days 1-30), own (days 31-60) and improve (days 61-90), with clear goals and measures for each phase.

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

Listen and learn: understand why the project exists, meet every key stakeholder, run an honest health check of schedule, cost, scope and risk, meet the team and deliver one small quick win.

What should a manager do in the first 90 days?

Learn the context in the first month, take ownership of governance, planning and risk in the second, and improve how the team works in the third, ending with a 90-day review for the sponsor.

Can you give an example of a 90-day plan?

Yes. The example above covers a project manager joining an IT delivery project, and the free template includes the full version with actions, outputs, owners and due dates.

How long should a 30-60-90 day plan be?

One page, or three slides, is enough. Aim for three to five goals per phase, each with a clear measure of done.