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

The short answer

A 30-60-90 day plan for a program manager covers the first three months in a new program. Days 1 to 30 are for mapping the projects, their dependencies and the people. Days 31 to 60 are for setting up governance. Days 61 to 90 are for the first trade-off you put to the sponsor, tied to the benefits.

Practice your answers in Claude with Interview Coach, free

How a program plan differs from a project plan

A project manager's first 90 days center on one plan, one team and one go-live. A program manager inherits several projects at once, each with its own manager, plan and risks. The job is the space between them.

So the program plan asks different questions. Which projects depend on which? Who decides when two projects want the same people? What does the sponsor expect the program to deliver, beyond the projects' own dates? A plan that answers those questions shows the hiring manager you know what the role is.

Days 1 to 30: map the program

The first month is for learning, with a record at the end of it.

• Meet each project manager. Ask about their plan, their top risks and what they need from the program.
• Meet the sponsor and the steering group. Ask what the program must deliver and what would count as a good first quarter.
• Read the record. The business case, the program plan, the last steering packs, the RAID logs of each project.
• Draw the dependency map. One page that shows which project waits on which, and when.

Checkpoint: the dependency map, reviewed with the project managers in the first program review. A map that the project managers agree with is worth more than one you drew alone.

Days 31 to 60: set up governance

The second month is for the way decisions get made. Many programs have meetings but no clear place where cross-project decisions land.

• Agree on the forums. A program review with the project managers and a steering forum with the sponsor, each with a set rhythm.
• Agree on what goes where. Which decisions a project manager makes alone, which come to the program review, which go to the sponsor.
• Set up one decision log. Every cross-project decision, its reason and its owner, in one place.
• Take over the program report. One report for the sponsor that rolls up the projects and shows the dependencies at risk.

Checkpoint: the first steering forum held, with its decisions in the log. The log shows that governance works, not only that it exists.

Days 61 to 90: the first trade-off

The third month is for leading. A program manager earns trust by handling a conflict between projects in the open.

• Bring one trade-off to the sponsor. Two projects want the same test window, or one slips and pushes another. Lay out the options and their effect on the benefits.
• Tie the projects to benefits. Agree with the sponsor how the program will show it delivered, beyond go-live dates.
• Review the first 90 days with your manager against the checkpoints you set.

Checkpoint: the trade-off decision and its reason in the decision log, and a first benefits view agreed with the sponsor.

An illustrative program manager plan

The example is a program manager who joins a claims modernization program of four dependent projects.

Illustrative, not a real client.

Each row pairs one action with one record a person can see. A real plan can hold more rows, but every one still needs its record.

Build yours from the job posting

A plan for an interview should answer the posting. The free plan builder reads one job posting and drafts a skeleton from it. You get what to learn in the first 30 days and quick wins tied to the problems the posting names. Day 90 targets stay yours to set.

Build your plan from a job posting

Before you use it, mark the program words in the posting: dependencies, governance, roadmap, benefits, portfolio. Those words tell you which phase the hiring manager will ask about.

Weak spots in a program manager plan

• A project plan with a new title. If every action is about one schedule, the plan reads as a project manager's.
• Governance with no decisions. Meetings in the calendar do not show governance. The decision log does.
• Benefits promised on day 1. Promise to agree how benefits will be tracked, not a figure you have not seen.
• No project managers in the plan. They do most of the work. A plan that never names them misses the role.

When the interviewer asks about your plan

The question can be direct, such as "What would you do in your first 90 days?" It can also come as a case about a program in trouble. In both, the interviewer listens for the order of your steps and the records you would produce.

Practice the follow-up questions too. "How would you handle two project managers who disagree on a date?" is a dependency question in disguise. The program manager interview questions and the program dependency question guide show how to answer it.

The way you present the plan matters as much as the plan. The guide to presenting a 30-60-90 day plan covers the five minutes in the room.

Keep going

• 30-60-90 day plan examples
• How to present a 30-60-90 day plan in an interview
• Program manager interview questions
• From project manager to program manager

Last updated: October 24, 2026