How it worksSupportPricingFAQ
Resources
BlogBest Practices
About
Talk to usLogin
← Back to the blog

How to prioritize a project portfolio: decisions program managers can justify

August 6, 2026 · 5 min read

There are countless prioritization frameworks by now, and yet most portfolio boards still end up with the HiPPO, the highest paid person's opinion. That is less bad than its reputation, because experience is a legitimate criterion. It only becomes a problem when that opinion has to decide on poor information.

Portfolio prioritization rarely fails because of the formula. It fails because of the information gap between business units and decision-makers.

The real problem is the information gap

The frameworks themselves are usually not to blame. WSJF, scoring matrix, cost-benefit chart: the formulas are not wrong, they just don't solve the problem that makes prioritization fail in practice. The business unit understands the technology and sits on data the decision-makers don't have. The decision-makers understand the financial metrics and act along a strategy that the business unit, in turn, doesn't know. So the business unit may misjudge how a product will be sold, while controlling doesn't see that a particular feature can change the entire target group. In the end, neither side can make a good assessment, and every prioritization falls into that gap, no matter which framework is on the slides.

The solution is basically known: the business unit that understands the solution has to be brought to a level where it speaks the language of the decision-makers, meaning financial metrics and strategy. With Excel templates and scoring models, though, this regularly fails in practice, because they are either inflexible or hard to understand. Bayescase, our innovation management software, is at its core the attempt to make exactly this translation practical: the business unit describes its project, and what comes out is a business case in the language of the decision-makers.

How a board prioritizes in a way people can follow

The setup is unspectacular. There is a budget for the period, set in advance, and there are one, at most two criteria, also set in advance, that decisions are based on, with a clear justification for why exactly these. Usually you work with NPV.

Then all projects are triaged: definite yes, maybe, definite no. This can happen almost automatically, based on the available budget. Part of the budget (e.g. 70%, you choose the share yourself) is filled with the definite yeses. For the rest, you deliberately put twice as many projects into the maybe pile as still fit into the budget, and all of these maybes get discussed. That is where prioritization matters most, right at the cutoff, and that is where the softer factors have their legitimate place: strategy, experience, the judgment of the experienced people in the room. The more time you want to spend on this discussion, the smaller you make the share of definite yeses.

The result is always a prioritized list. And it is not a machine with a bouncer at the door: management can pull up a strategically important project at any time, even from the definite nos, because a business case can never capture everything. All that matters is that whoever does this sees which projects they are deprioritizing for it. And that everyone involved keeps their common sense.

And the must-do projects?

For compliance, regulation and similar obligations, there are two ways to read it. Either you calculate a business case for them too, which is more revealing than it sounds, because compliance is more negotiable in some places than you'd think, and the extreme cases (cost of a burned-down data center times probability of occurrence) make it into the budget anyway. Or you run them outside the portfolio and reduce the budget by the corresponding amount. Both are defensible. Just know this: every now and then it turns out that a must-do project isn't such a must-have after all. Then the calculation has paid off.

Stopping is part of prioritization

The most uncomfortable part comes after the budget round. Failing projects are almost always stopped too late, because people are attached to their projects, and for every old project that keeps running, a new, promising one doesn't get done. This portfolio hygiene matters a lot more than its place on the agenda suggests. It gets easier when every project has a set, P&L-relevant goal from the start, along with clear kill criteria (for example: a probability of reaching the goal below 20% means re-evaluation or stop). Then you track it, and when something gets stopped, everyone can see why. That takes the personal element out of the decision, and that is exactly what stopping otherwise fails on.

Frequently asked questions

How do I prioritize a project portfolio in a way that is transparent and easy to justify?
With a budget set in advance and one, at most two criteria set in advance (usually NPV), against which all projects are triaged: definite yes, maybe, definite no. Part of the budget is filled with the definite yeses, the maybe pile deliberately gets twice as many projects as still fit into the budget, and all of these are discussed, because prioritization matters most at the cutoff. Soft factors like strategy and experience change the order there. The result is a prioritized list that keeps visible which project gives way for which other one.
How should must-do projects like compliance and regulatory work be handled in a project portfolio?
Either you calculate a business case for them too, because some obligations are more negotiable than you'd think and the real extreme cases make it into the budget anyway. Or you run them outside the portfolio and reduce the available budget accordingly. Both work, as long as the must-do projects don't bypass prioritization unchecked.
When should you stop a running project?
When a P&L-relevant goal set in advance, with clear kill criteria, is missed, for example as soon as the probability of reaching the goal falls below 20%. If the goal and criteria are agreed before the start and tracked continuously, everyone can see why a project is stopped, and the decision loses the personal element that otherwise makes stopping fail.
Lukas Mayer

Written by

Lukas Mayer

Co-Founder & COO, Bayescase

What will your strategy deliver?

In a short conversation we take one of your initiatives and show how an idea becomes a business case with targets and tracking.

Talk to usarrow_forward