Portfolio Management
Portfolio management is the practice of deciding which projects an organisation runs, in what order, and with what funding. It works one level above delivery: rather than asking whether a project is on track, it asks whether the project should still be running at all, and what it is displacing.
What it contains
A portfolio is a register of every project and programme an organisation has committed to, plus the ones it is considering. For each entry the register typically records an owner, a sponsor, a stage, a budget and a forecast, a benefit or rationale, a strategic theme, and a health status. Alongside the register sit three things: a prioritisation method, a funding position, and a resource view showing which projects are competing for the same people.
The prioritisation method is usually a weighted scorecard — criteria such as strategic fit, regulatory necessity, financial return, risk of not doing it, and delivery confidence, each weighted and scored. The output is not an answer. It is an ordered list that makes the argument visible.
How it is used
Portfolio management runs on a slower cycle than project reporting. Intake happens when new demand arrives; prioritisation happens at a fixed review, often quarterly; reporting happens monthly. At intake, a proposal arrives with a business case and enough estimate to be scored. At review, the ordered list is compared against available funding and capacity, and a line is drawn.
The register also supports the questions that only exist at portfolio level: which projects depend on the same platform freeze, how much of the change budget is committed versus spent, which sponsor owns the most in-flight work, and how many projects are amber for the same underlying reason. A portfolio dashboard exists to answer those from one register rather than from twelve status decks.
Stopping projects is part of the practice, and the hardest part. A portfolio review that has never stopped anything is a reporting meeting rather than a decision-making one. The register records the decision and the date; what happens afterwards is closure, whether the project finished or was cancelled.
Where it goes wrong
Portfolios drift by accretion. Projects are added at intake and rarely removed, so the list grows until the organisation is running more work than it can staff. Nothing is formally cancelled; things simply slow down. The symptom is a portfolio where most projects are technically active and few are making measurable progress.
The second failure is scoring theatre. A weighted scorecard is built, everyone learns which criteria carry weight, and business cases are written backwards from the score they need. The scorecard still has value as a record of the reasoning, but it stops discriminating between proposals.
The third is a portfolio managed without a capacity view. Funding is approved on the assumption that people exist to do the work, and the constraint only appears later as slipping dates across unrelated projects. Portfolio decisions that ignore the resource position are decisions about money, not about delivery.
A fourth: benefits are stated at approval and never revisited. The portfolio then has no way to learn which kinds of investment actually paid back, and every intake cycle repeats the same optimism.
Related terms
Programme management co-ordinates a group of related projects towards a shared outcome; a portfolio is not required to be related in any way beyond sharing funding and capacity. PMO is the function that usually maintains the register and runs the reporting cycle. Business case is the artefact that carries a proposal into the portfolio. Capacity planning supplies the constraint that portfolio decisions are made against. Stage gate is where a project's continued funding is confirmed or withdrawn.
Questions
What is the difference between a portfolio and a programme?
A programme is a set of related projects delivering one outcome. A portfolio is everything the organisation has committed to, related or not, held together by shared funding and shared people.
How often should a portfolio be reviewed?
Most organisations review prioritisation quarterly and report health monthly. Reviewing prioritisation more often than the funding cycle tends to produce churn rather than decisions.
Who owns the portfolio?
Usually an executive or investment board, with the PMO administering the register and the reporting. The distinction matters: the PMO supplies the data, the board makes the call.
Does portfolio management require a tool?
No. A register with consistent fields and an agreed scoring method works in a spreadsheet. Tools help when the number of projects or the reporting frequency makes manual consolidation impractical.