Project Portfolio Prioritization When Everyone Is P1

Here's the uncomfortable pattern. Every project on the board is marked Priority One, which means none of them are. A priority list where everything is priority one isn't a list, it's a refusal to choose, and it usually means whoever asked the loudest, not whoever built the strongest case, is getting the resources this quarter.

The direct answer: project portfolio prioritization works by scoring every project on three numbers, value, confidence, and capacity cost, ranking by the composite, then capping the active list at real capacity. Publish the ranked list alongside a stop list naming exactly what didn't make the cut and why. A model beats an argument because the sponsors helped build it before they saw where their project landed.

Why "Everything Is Priority One" Isn't a Priority List

Project portfolio management exists specifically to make this trade-off explicit instead of implicit, choosing which projects get funded given finite capacity, rather than pretending every request can be funded at once. A label only works if it excludes something. When every project carries the same top label, the label has stopped doing its job, and what fills the gap is politics: whoever escalates hardest, whoever has the sponsor with the most tenure, or whoever asked first wins the argument by default. The fix isn't a better meeting. It's replacing the label with a number every project earns the same way.

Project Portfolio Prioritization on Three Numbers

Score each project on value, confidence, and capacity cost, then rank by value times confidence, divided by capacity cost.

Score	What it captures	Who scores it
Value (1-5)	Strategic payoff if the project succeeds: revenue, risk reduction, or a hard external deadline	The sponsor, since they own the business case
Confidence (1-5)	How likely the team is to hit the value estimate, based on similar past projects	The PMO, using estimating history, not the sponsor's optimism
Capacity cost (FTE-weeks)	How much of your actual delivery capacity the project consumes end to end	The resource or delivery lead who owns the estimate

Composite score = (value × confidence) ÷ capacity cost. A high-value project that eats enormous capacity for a coin-flip outcome scores lower than a modest project the team can deliver with near certainty for a fraction of the resource cost, which is usually the opposite of how the loudest voice in the room would rank it.

The diagram below shows six scored projects ranked in order, with the capacity cut line separating what gets funded from what gets stopped.

Capping the Active List to Real Capacity

The cut line in the diagram isn't arbitrary; it sits where the sum of capacity cost for the ranked projects equals the delivery team's actual available capacity for the quarter, not the wished-for capacity of a fully staffed team that doesn't exist. Most portfolios run oversubscribed because nobody totals the capacity cost column against the real number of delivery weeks available; every project gets approved individually, and the collision only shows up months later as missed dates across the board. Total the capacity cost of every scored project, total the team's actual available FTE-weeks, and draw the line where the running sum crosses that number.

Publishing the Stop List

1. Rank the full list by composite score, not by department or sponsor seniority, so the line is visibly the same rule for everyone.
2. Publish the stop list by name, with the score that put each project below the line, not a vague "deferred" bucket that lets a project linger half-staffed indefinitely.
3. State the re-review date for every stopped project, so "stopped" reads as "not this quarter" instead of "never," which is what makes the list politically survivable.
4. Hold the line for the quarter. A stop list that gets overridden by the first escalation email trains sponsors to escalate instead of to build a stronger case for the next ranking cycle.

Sponsors accept a low rank far more often than they accept a subjective "not now." Ranking six projects works from a whiteboard, but the math changes at scale: the PMO tipping point at three projects covers where informal tracking stops working entirely, and migrating an existing pairwise prioritization model covers the version of this problem PMOs inherit from Project Online's portfolio analyzer. Both assume the same starting discipline this post lays out: a model beats an argument, every time the model is actually enforced. The wider PMO practice library covers the governance and estimating disciplines that scoring model depends on.

A portfolio can have a perfect scoring model and still fail to hold the line if governance maturity is too low to enforce it, the gap between publishing a stop list and actually stopping work on it. That gap shows up as a weak governance score before it shows up as a blown quarter.

Check whether your governance can hold the line Run the free PMO Maturity Assessment to see whether your governance dimension is strong enough to enforce a published stop list, not just produce one. → Take the free PMO Maturity Assessment

Microsoft Project Online™ is a trademark of Microsoft Corporation. Onplana is not affiliated with Microsoft.