30-60-90 day plan examples for program, project and product managers

The short answer

A 30-60-90 day plan is a one-page plan for your first three months in a new role. For a project, program or product manager, the first 30 days are for learning. Days 31 to 60 are for contributing, and days 61 to 90 for leading. Each phase ends with a checkpoint another person can see, such as a status report.

A hiring manager or a new sponsor can check a record. They cannot check a promise. So each example on the page pairs one action with one record that shows the action happened.

Practice your answers in Claude with Interview Coach, free

The 30-60-90 day plan format: what goes in each phase

The three phases follow one order: learn, contribute, lead. Each one has a different goal.

• Days 1-30, learn. Meet the sponsor, the team and the people who depend on your work. Read the plan, the budget, the risk log and the last status reports. Ask your manager what a good first quarter looks like.
• Days 31-60, contribute. Take over one recurring duty, such as the status report or the weekly risk review. Fix one problem you found in the first month. Agree on how you report and to whom.
• Days 61-90, lead. Make one decision that changes the plan, and record it. Propose one change to how the work runs. Review the first 90 days with your manager against the checkpoints you set.

A checkpoint is a record, not a feeling. "Built trust with the team" is not a checkpoint. "Held a 1:1 with each of the 6 people on the team" is a checkpoint, because the meeting notes exist.

Three 30-60-90 day plan examples

The table shows three illustrative plans: a project manager mid-project, a program manager with dependent projects, and a product manager with a product line.

Illustrative, not a real client.

Each row keeps to one action per phase, so the pattern is easy to read. A real plan can hold 2 or 3 actions per phase. Each action still needs its own checkpoint.

The three roles differ in where the first record comes from. A project manager starts from the plan and the RAID log. A program manager starts from the links between projects. A product manager starts from customers and the metric the team is measured on.

A 30-60-90 day plan for a new manager

A first manager role adds people to the plan. The delivery work stays the same, but now some of the people on it report to you. Three items belong in the plan of a new manager.

• 1:1 meetings. In the first 30 days, hold a 1:1 with each person who reports to you. Ask what they work on, what slows them down and what they need from a manager. Checkpoint: a note of each meeting and a regular time agreed with each person.
• Team rules. By day 60, agree with the team how work is assigned, how people ask for help and where decisions are recorded. Write the rules in one place. Checkpoint: the team agreement, shared with your manager.
• The first people decision. By day 90, you may need to decide about a person: a task to reassign, a hire to make or feedback to give. Plan it with your manager before you act. Checkpoint: the decision and its reason, agreed with your manager.

A new manager who changes the team rules in week 1 can lose the trust the 1:1 meetings were meant to build. Listen first, then change one rule at a time.

How to write yours from the job posting

Write your plan from the job posting, not from a list of good habits. The posting names what the hiring manager needs in the first months.

1. Copy 3 to 5 requirements from the job posting into the first column of your plan.
2. Write one action for each requirement, in the phase where you would do it.
3. Name the record that will show each action happened, such as a status report or a RAID log.
4. Name the person who would confirm each checkpoint, such as the sponsor or your manager.
5. Write one risk for each phase and what you would do if it happened.

A plan built this way answers the posting line by line, so the interviewer can see the match.

Build your plan from a job posting

Weak spots in a 30-60-90 day plan

Weak plans tend to break in the same places. Each weak spot has a direct fix.

• Goals without a record. "Build relationships with stakeholders" names no person and no meeting. Write "Meet the sponsor, the finance lead and the 2 vendor leads by day 20, and agree on a reporting rhythm with each."
• Results you cannot know yet. "Reduce the backlog by half by day 90" promises a result before you have seen the work. Promise the review instead: "Review the backlog with the team by day 45 and agree on a target with the sponsor."
• No people in the plan. A plan of documents says nothing about the team. Name the 1:1 meetings and the first team review.
• Changes in the first week. A process change in week 1 tells the reader you act before you listen. Put the first change in days 31 to 60.
• Too many actions. Twelve actions in 30 days cannot all have checkpoints. Keep 2 or 3 per phase.

Where the plan comes up in interviews

Hiring managers often ask about the first 90 days. The question can be direct: "What would you do in your first 90 days?" It can also be part of a case about a project in trouble. In both forms, the interviewer listens for the order of your steps and for the records you would produce.

The interview question pages for each role show the other questions you can expect:

• Project manager interview questions
• Program manager interview questions
• Product manager interview questions

When the hiring manager asks you to bring a plan to the interview, the way you present it matters as much as the plan.

How to present a 30-60-90 day plan in an interview

Keep going

• How to present a 30-60-90 day plan in an interview
• Project manager interview questions
• Program manager interview questions
• Product manager interview questions

Last updated: October 16, 2026