The program management process: five phases, and how to explain yours in an interview

Last updated:

The short answer

The program management process runs a group of related projects toward one set of benefits. It usually moves through five phases: define the program, set it up, deliver the projects, hand the results to the business and close. In an interview, describe your own process through one program you ran, phase by phase.

Key points

  • A program exists for benefits that no single project delivers alone.
  • The five phases are define, set up, deliver, transition and close.
  • Governance runs through every phase: who decides what, and in which forum.
  • In an interview, tell your process as one real program, with the decisions that were yours.

How a program differs from a project

A project delivers an output, such as a system or a building. A program coordinates several projects so that the business gets an outcome, such as faster claims or a merged customer base.

AreaProjectProgram
GoalAn output, on a date, within a budgetBenefits that need several outputs together
TimeEnds when the output is acceptedOften runs until the benefits are measured
PlanOne schedule and critical pathLinked project plans and their dependencies
DecisionsThe project sponsor and the project managerA steering group, several sponsors and the program manager
Success measureScope, date and costThe benefit measure in the business case

The comparison of program manager, project manager and TPM roles shows how the jobs differ day to day.

The five phases of the program management process

PhaseWhat the program manager doesRecords it usually leaves
DefineAgrees the goal, the benefits and the boundaries with the sponsorBusiness case, program charter, benefits map
Set upBuilds the structure: projects, roles, forums and reportingGovernance plan, roadmap, decision rights
DeliverRuns the projects as one plan and settles what crosses themIntegrated plan, dependency log, risk log, steering minutes
TransitionHands the new ways of working to the businessReadiness checklist, handover plan, training records
CloseMeasures the benefits and shuts the program downBenefits report, lessons learned, closure note

The names differ by company. Some call the first phase initiation or mobilization, and some merge transition into delivery. The work in each phase stays much the same.

Phase 1: define the program

The program starts with a reason. A sponsor wants an outcome that one project cannot reach, such as one customer system after a merger.

  • Agree the goal in one sentence and the benefits that will show it.
  • Name the measure for each benefit and where its baseline lives.
  • Set the boundaries: what is in the program and what stays out.
  • Identify the projects the program will need, even if some start later.

Phase 2: set up the structure

Before projects run at full speed, the program needs a way to make decisions.

  • Set the governance: a steering group, its members, how often it meets and what it decides.
  • Write the decision rights: what a project manager decides, what the program manager decides and what goes to steering.
  • Build a roadmap that shows the projects, their order and the main milestones.
  • Agree one reporting format, so every project reports the same way.

Phase 3: deliver the projects as one plan

Most of the program's life sits in delivery. The program manager does not run each project; the project managers do. The program manager keeps them working as one.

  • Keep an integrated plan that shows the handoffs between projects.
  • Run a dependency review with an owner for each cross-project item.
  • Take the decisions that cross projects to steering, with options.
  • Track the benefits measures while delivery is still running.

Phases 4 and 5: transition and close

A program can deliver every project and still miss its benefits, if the business does not adopt the change. Transition is where adoption is planned: training, support and the handover of new processes to their owners.

Closing comes once the benefits are measured or handed to a business owner who will track them. The program manager writes the benefits report and the lessons learned, then releases the people and the budget.

How to answer "walk me through your program management process"

Interviewers ask this to see whether you work at program level. A list of phases from a textbook answers it poorly. One real program, told phase by phase, answers it well.

  1. Name the program, its goal and its size in two sentences.
  2. Say how it was defined: the business case and the benefit measure.
  3. Describe the governance you set up or inherited, and one decision it made.
  4. Give one moment in delivery where projects collided, and what you did.
  5. Say how the benefits were measured and handed over.
  6. Close with one thing you would set up earlier next time.

Keep it to two or three minutes. The panel will pick a phase and ask for detail, so prepare one story for each phase.

Answer examples

Each answer below gets every mark of its rubric in the answer check of Interview Coach.

The set up phase, a governance change (change rubric):

When I took over a retail store systems program, each of the four project managers reported to the sponsor separately, and decisions came out of hallway conversations. I proposed one fortnightly steering meeting with written decision rights for each role. I drafted the rights with the project managers and I agreed them with the sponsor in one session. I ran the forum and I kept a decision log. Within one quarter, decisions taken outside the forum fell from nine a month to one, per the decision log.

The deliver phase, a collision between projects (story rubric):

When I ran a hospital records program, the network upgrade and the new records system both needed the same weekend at three clinics. Neither project manager wanted to move. I laid out both plans with the clinic managers and I showed which order carried less risk for patients. I proposed the network first and the records system two weeks later. The sponsor approved it at steering. All three clinics went live on the new dates with no downtime outside the window, per the change calendar.

Illustrative, not a real client.

Mistakes when you describe your process

  • Reciting phases. The panel knows the phases. They want to know what you did in them.
  • Project language only. Schedules and tasks belong to the projects. Talk about handoffs, forums and benefits.
  • No benefits. A program process that ends at go-live leaves out the reason the program existed.
  • No decision rights. Say who decided what. In my experience, unclear decisions hurt a program more often than a weak plan does.

Practice before the interview

Write your own program in six lines, one per step of the answer above. Then say it out loud and check one story with the free STAR answer check. It marks a missing result, a missing record or an answer told only with we.

Practice with Interview Coach in Claude

Interview Coach reads your resume and a program manager posting, then asks about the programs on your own resume. Write your answer the way you would say it and ask for a check.

  • Paste your resume and the job posting. Interview Coach returns the lines a hiring manager is likely to ask about, each as a question that quotes your own line, with the points a strong answer covers.
  • It matches the requirements of the posting to your resume and turns the gaps into questions to prepare.
  • Write one answer at a time and ask for a check. It looks for a situation, your own action, a result and a before and after figure or a named record. It does not judge whether the story is true.

Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.

Free in Claude, no account. We do not store the text you send through it.

Questions

What are the phases of the program management process?

Most programs move through five phases: define, set up, deliver, transition and close. Companies name them differently and sometimes merge two of them. The work stays similar: agree the benefits, build governance, deliver as one plan and measure the result.

What does a program manager do that a project manager does not?

A program manager coordinates several projects toward shared benefits. That means owning the dependencies between projects, running the forums where cross-project decisions are made and tracking the benefits. Each project still has its own manager.

How long should my answer about my program management process be?

Two to three minutes for the first answer. Tell one real program phase by phase, then let the panel choose where to go deeper. Have one story ready for each phase.

Keep going