30-60-90 day plan for program managers
On this page
- How is a program manager's first 90 days different from a project manager's?
- What does the 30-60-90 day plan look like?
- What goes in the program's operating documents?
- Which numbers should a new program manager baseline?
- What does "on track" look like at day 30, 60 and 90?
- A filled example
- How should the hiring manager use this plan in the final interview?
- What should the sponsor ask at the check-ins?
- What the sponsor owes a new program manager
- Common mistakes
- Adapting the plan
- Questions people ask
A 30-60-90 day plan for a new program manager should list every project in the program, map the dependencies between them and compare the promised benefits with what the projects will deliver in the first 30 days, take over the governance rhythm and agree any change in scope, funding or sequence with the sponsor in days 31-60, and present a program roadmap and benefits register the sponsor and project managers both accept by day 90. Unlike a project manager, a program manager is judged on how related projects add up to a business result, not on one schedule.
This page is for the sponsor, director, PMO lead or executive hiring a program manager, technical program manager or portfolio-facing delivery lead. For a single project, the 30-60-90 day plan for project managers covers the RAID log, rebaselining and status reporting this plan builds on. If the role runs the leadership team's operating rhythm instead of a defined program, the 30-60-90 day plan for chiefs of staff fits better.
How is a program manager's first 90 days different from a project manager's?
PMI's PgMP handbook (revised March 11, 2024) describes program managers as accountable for the coordinated management of multiple related projects directed toward strategic objectives, sharing resources among those projects and keeping scope aligned with the business result. In practice that changes what a new hire has to learn first.
| Area | Project manager | Program manager |
|---|---|---|
| What success means | Scope delivered on time and budget | The benefits in the business case realized, across several projects |
| Schedule | One schedule and its critical path | A roadmap of project milestones and the handoffs between them |
| Risk | The project's RAID log | Risks that cross projects, and the threshold at which a project escalates to the program |
| People and money | Works within an allocated budget and team | Moves shared people and funding between projects |
| Governance | Reports to a sponsor or steering group | Runs the steering group and its decision log |
| Stakeholders | The project team and its users | Several business owners, vendors and often other programs |
The closest occupation in the BLS Occupational Outlook Handbook is project management specialists, with a national median annual wage of $102,320 in May 2025 and projected employment growth of 7 percent from 2025 to 2035. The handbook has no separate entry for program managers.
What does the 30-60-90 day plan look like?
30-60-90 day plan — [Name], Program Manager, [program]
Reports to: [sponsor / director / PMO lead] Start date: [date]
Projects in the program: [N] Project managers: [names]
Budget: [amount] Business case approved: [date]
Steering group: [members], meets [frequency]
Next funding or stage-gate decision: [date]
DAYS 1-30 — Find out what the program really is
Goals:
- Read the business case, charter, last steering packs and
each project's status report and RAID log
- One-to-one with the sponsor, each project manager, each
business owner and the main vendors
- Program inventory: every project, owner, status, budget,
next milestone and confidence in it
- Dependency map: every handoff between projects, with the
date the receiving project needs it
- Benefits check: what the business case promised, which
project delivers each benefit, how and when it is measured
Deliverables by day 30:
- Program reassessment memo to the sponsor
- Program inventory and dependency map version 1
DAYS 31-60 — Take over governance
Goals:
- Run the steering group: one-page program status, decisions
requested, decision log kept
- Set the escalation threshold: what a project decides alone
and what comes to the program
- Weekly program meeting with the project managers on
cross-project risks and dependencies only
- Bring any scope, funding or sequence change to the sponsor
with its cost and effect on benefits
- Resource view: who is shared across projects and where
demand exceeds capacity
Deliverables by day 60:
- Decision on any change the reassessment showed is needed
- Escalation rules agreed with the project managers
DAYS 61-90 — Own the roadmap and the benefits
Goals:
- Publish the program roadmap: all project milestones and
handoffs on one page
- Benefits register with owner, measure, baseline and the date
each benefit is measured
- Resolve one cross-project dependency that was stuck
- Plan the next stage gate or funding request
Deliverables by day 90:
- Roadmap and benefits register accepted by the sponsor
- A forecast the project managers say they believe
Check-ins: weekly with [sponsor]; reviews at day 30, 60 and 90.What goes in the program's operating documents?
A program runs on a handful of documents above the project level. A new program manager rarely inherits all of them in usable shape; the plan rebuilds them in order of risk.
| Document | What it holds | Why the new program manager needs it |
|---|---|---|
| Program inventory | Each project, its owner, budget, status, next milestone and the project manager's confidence | Programs collect projects nobody remembers approving, and some that quietly stopped |
| Dependency map | Every handoff between projects: what, from whom, to whom, by when | Most program slips start as one project waiting on another |
| Benefits register | Each promised benefit, its owner in the business, measure, baseline and measurement date | Projects can finish on time while the benefit never arrives |
| Program RAID log | Risks, assumptions, issues and dependencies that cross projects, with the escalation threshold | Keeps the program meeting off single-project detail |
| Resource view | Shared people and teams, their allocation across projects, and gaps | The same specialist is often planned at full time on two projects |
| Decision log | Every steering decision, its date, who made it and what it changed | Stops settled questions coming back at every meeting |
Which numbers should a new program manager baseline?
The measures are examples. Pick the few the sponsor already asks about and report them the same way every month.
| Measure (examples only) | The question behind it |
|---|---|
| Program milestones met against the current baseline, by project | Is the program delivering what it said it would, when it said? |
| Cross-project dependencies due in the next 90 days, and how many are at risk | Where will the next slip come from? |
| Benefits on track against the business case, by benefit | Will the program pay for itself? |
| Spend and commitments against budget, program and project level | Is money where the priorities are? |
| Shared roles planned above their capacity | Which plans are fiction? |
| Decisions waiting on the steering group, and their age | Is governance helping or blocking? |
What does "on track" look like at day 30, 60 and 90?
| Checkpoint | On track | Worth a direct conversation |
|---|---|---|
| Day 30 | The reassessment memo names the dependencies and benefits at risk, with evidence from the project managers; every project is on the inventory | The memo summarizes project status reports; benefits not mentioned; has not met the business owners |
| Day 60 | Steering meetings end with decisions in the log; escalation rules agreed; any needed change taken to the sponsor with its cost | Steering is a status readout; the program manager is re-running project meetings |
| Day 90 | Roadmap and benefits register accepted; a stuck dependency resolved; project managers bring cross-project problems early | A roadmap the project managers do not recognize; benefits still described only in the business case |
A filled example
Program manager: Renee Okafor (invented), joining a regional insurer's claims modernization program of five projects (a new claims platform, data migration, document management, a customer portal and training), reporting to the chief operating officer. All details are examples.
Day 30: The dependency map showed the customer portal planned to launch two months before the claims platform it reads from. The business case counted a reduction in claims handling time that no project owned. Two projects shared one integration architect, each planning on her full time.
Day 60: The steering group approved resequencing the portal behind the platform, with the cost of the delay recorded in the decision log. The claims director accepted ownership of the handling-time benefit and a measurement date six months after go-live. The architect's time was split by written agreement between the two project managers.
Day 90: The one-page roadmap replaced five separate status decks at steering. The data migration handoff that had been stuck for a month was settled with the platform vendor. The COO accepted the benefits register and the plan for the next funding gate.
How should the hiring manager use this plan in the final interview?
Give every finalist the same brief: the business case summary, the list of projects with their status, the budget and one known conflict between projects. Score the plans with the rubric in how to evaluate a 30-60-90 day plan in an interview. A strong plan maps dependencies and benefits before reporting status. Questions that test it:
- "Two of our projects need the same team in the same quarter. How do you decide, and who signs off?"
- "Every project is green but the program is late. How is that possible, and what do you do?"
- "The business owner says the benefit in the business case was never realistic. What happens next?"
- "What would you stop the project managers bringing to the program meeting?"
The project manager phone screen questions and the IT project manager screening questions cover the delivery basics a program manager candidate should also show.
What should the sponsor ask at the check-ins?
- Day 30: Which dependency worries you most? Which benefit has no owner?
- Day 60: What decisions do you need from me, and by when? What will the project managers now decide without you?
- Day 90: What does the roadmap say we deliver this year? When will we first measure a benefit, and who will measure it?
What the sponsor owes a new program manager
- Authority in writing over sequencing, shared resources and the program's contingency, within agreed limits.
- An introduction to the project managers and business owners that makes clear the program manager speaks for the program.
- The business case, the funding conditions and any promises made to the board or customers.
- Steering members who attend and decide, and backing when the reassessment brings bad news.
Common mistakes
- Managing the projects instead of the program. A program manager in every project meeting leaves the cross-project work undone.
- Adding up project status. Five green projects can still make a late program if their handoffs do not line up.
- Treating benefits as the business owner's problem. If no one owns a benefit by day 90, it will not be measured.
- Steering without decisions. A steering meeting that only hears status teaches projects to stop escalating.
Adapting the plan
- Federally funded programs: under the Uniform Guidance as of November 2026, recipients must relate financial data to program accomplishments when they report performance, and an agency or pass-through entity may not require performance reports more often than quarterly unless a specific condition applies (2 CFR 200.329). Final reports are due within 120 calendar days after the period of performance ends, or 90 days for subrecipients reporting to a pass-through entity (2 CFR 200.344). Put both dates on the roadmap; the 30-60-90 day plan for nonprofit executive directors covers the audit side. This is not legal advice.
- Technical program managers: replace the benefits register's business measures with release and platform measures where needed, and add the engineering managers to the month-one meetings; where teams run scrum, the scrum master screening questions help separate the roles.
- Construction and capital programs: add contract and change-order exposure by project; the 30-60-90 day plan for construction project managers covers the money cycle each project runs.
- Product-led companies: where product managers own what is built, agree in month one that the program manager owns sequencing and dependencies, not the roadmap's content.
Questions people ask
What should a new program manager do in the first 30 days?
Read the business case and the program's charter, meet the sponsor and every project manager and workstream lead, list every project in the program with its status, owner and next milestone, map the dependencies between projects, and compare the benefits the business case promised with what the projects will deliver. The month ends with a program reassessment memo to the sponsor.
What is the difference between a program manager and a project manager?
A project manager delivers one defined scope to a date and a budget. A program manager coordinates several related projects toward a business result, decides how shared people and money move between them, manages the dependencies between projects, and answers for the benefits the program was funded to deliver. PMI's program management role description says program managers assign project managers to run the component projects.
What should a program manager present at 90 days?
A refreshed program roadmap with every project's milestones on one page, a dependency map with owners for each cross-project handoff, a benefits register showing which benefits are on track and when they will be measured, the governance calendar the sponsor agreed, and any change to scope, funding or sequence the program needs, with its cost.
Do program managers need the PgMP certification?
It is not required for most roles. PMI's PgMP handbook, revised March 11, 2024, requires 48 months of project management experience or a PMP, plus 48 months of program management experience with a four-year degree or 84 months without one, all within the last 15 years, followed by a panel review and a multiple-choice exam. It shows sustained program experience, but a candidate's 30-60-90 day plan shows more about how they would run yours.