Expertise · PMO & portfolio

Making portfolio trade‑offs when capacity is finite

A project portfolio is not a list to be sorted by priority. It is a set of commitments that draw on the same teams, the same budgets, the same equipment. Making trade‑offs means deciding what you will not do, or not now, with a clear view of what that costs.

Cyril Verbrugghe, CEO and co-founderPublished November 10, 2026

Making portfolio trade-offs when capacity is finite

The problem: priorities without capacity

In many groups, the portfolio review looks like a ranking. Each project is scored on strategic value, urgency and risk, and the ordered list stands in for a decision. The trouble is that the list says nothing about feasibility. Ten "priority" projects can all call on the same engineering team in the same quarter.

Over‑allocation is then discovered through its symptoms: milestones that slip, resource trade‑offs made in crisis meetings, teams bouncing from one project to another as emergencies dictate. At that point, you are no longer choosing; you are reacting.

Why it happens

Capacity data is fragmented. Each project has its own schedule and workload; consolidating by discipline and by period takes manual work that few PMOs have time to do every month.

Value is rarely tracked. Bent Flyvbjerg reports a heuristic put forward by a project leader in his Oxford programs: benefits are what matter, cost and schedule are merely means. He observes that most projects do not even measure their benefits, and that the leaders who do get better results, including on budget and schedule.

Finally, trade‑offs are frozen. Once priorities have been voted on, the portfolio is rarely re‑simulated before the next cycle, even when the situation changes.

What changes: managing the portfolio as an investment

Three practices make the difference.

Continuously consolidate demand and capacity, by discipline, by period and by site, from the schedules of every project. Breaking points become visible months in advance.

Link each project to its expected value, and track it. A trade‑off between two projects competing for the same team is then settled on what each one delivers, not on whose project manager speaks the loudest.

Simulate before deciding. Pushing back a project, reinforcing a team, bringing in a subcontractor: each option affects the entire portfolio. The committee needs to see that before it rules.

That is what "managing your projects as an investment portfolio" means: knowing at all times what you are committing, what you expect in return, and what a different choice would cost.

In the field

In our portfolio management rollouts, consolidating demand and capacity translates into roughly +30% resource utilization and +25% more projects delivered on time. A global animal health laboratory took portfolio management of its entire worldwide R&D live in three months, across several hundred projects and dozens of disciplines.

Where to start

Pick the five most heavily loaded disciplines and consolidate their workload over twelve months, across all projects.
Compare that workload with actual capacity, net of leave and other activities.
Add an "expected benefit" line to each project, even a rough one.
At the next review, present two portfolio scenarios rather than a ranked list.

Frequently asked questions

What is portfolio capacity planning?

Consolidating, across all projects, the workload requested against the capacity available, by discipline and by period.

Do you need perfect data to consolidate?

No. A rough but regular consolidation is better than a perfect analysis once a year.

How long does it take to roll out portfolio management?

In practice, less than three months, including migration of existing projects and integration with your enterprise systems.

Sources

B. Flyvbjerg, "Heuristics for Better Project Leadership," Project Management Journal, 55(6), 2024.
OFFOLIO internal rollout measurements (resource utilization, on‑time delivery).