What's the difference between a project, a program and a portfolio?

What the interviewer is really testing

• Clarity. Can you explain something complex simply?
• Scale. Have you managed more than one project at a time, with shared people and dependencies?
• Business thinking. Do you think in outputs, or in business benefits?

The weak answer vs the strong answer

Here's the answer most candidates give: "A program is just a bigger project."

It's not about size. A program can be smaller than a big project. Saying "bigger" tells the interviewer you've never actually run a program.

A strong answer explains each level by what it delivers. Here's how.

The answer, level by level

First, a project. A project is a temporary effort that delivers a specific output, with a clear start, end, scope and budget. For example, building a new claims portal.

Second, a program. A program is a group of related projects managed together to deliver a business outcome that none of them could deliver alone. For example, a claims digital transformation: the new portal, an automated adjudication engine, a provider-data clean-up and the training roll-out. The program manager manages what sits between the projects: dependencies, shared resources, risks and the benefits.

Third, a portfolio. A portfolio is all the programs and projects in an organisation, or in a business unit, chosen and prioritised by strategic value and available budget. The portfolio question is: are we working on the right things?

So the key difference is this: projects deliver outputs, programs deliver benefits, and portfolios deliver strategy.

A real-world example

Let me make it real with a healthcare example. Picture a US health plan.

The portfolio is everything the plan invests in this year: regulatory work, member experience, cost reduction, and IT modernisation. Leadership ranks these by value and risk, and funds the top ones.

One funded program is to cut claim processing time from fourteen days to three. That's the benefit.

Under it sit four projects: the new claims portal, the auto-adjudication rules engine, the provider-data clean-up, and staff training.

Each project can finish on time and still fail the program. If the portal goes live but the provider data is still dirty, claims still get stuck, and the benefit never arrives. That's exactly why the program manager exists.