Ask a leadership team to rank its projects and you will usually get one of two answers: everything is critical, or whatever the loudest executive championed most recently goes first. Both are symptoms of the same problem. The organization has never agreed on what makes one project more valuable than another, so prioritization defaults to volume and politics.
Portfolio prioritization fixes that by making the criteria explicit and the tradeoffs visible. It will not remove judgment from the decision, and it should not. What it does is force an honest conversation about why one piece of work deserves capacity that another will not get.
Key takeaways
- Prioritization only works when it forces a real ranking, not a list where everything is "high."
- Pick a scoring model that matches your goal: weighted scoring for balance, cost of delay for time-sensitive work, value versus effort for quick wins.
- Score against capacity. A ranked list you cannot staff is just a wish list.
Start with the criteria, not the projects
Before scoring anything, agree on what you are optimizing for. Most portfolios weigh some mix of strategic alignment, financial return, risk reduction, and cost or effort. The exact set matters less than getting leadership to commit to it before they see the project names, because once the names are attached, the criteria mysteriously bend toward favorites.
Keep the list short. Four to six criteria is plenty. More than that and the scoring becomes a false precision exercise where small weighting changes swamp real differences.
Three scoring models worth knowing
Weighted scoring
You assign each criterion a weight, score every project against each criterion, and multiply. The project's total is the sum. Weighted scoring is the workhorse model because it is transparent and forces you to state how much strategic fit matters relative to, say, cost. Its weakness is that it can launder gut feelings into numbers, so the scoring conversation matters more than the arithmetic.
Value versus effort
Plot each project on two axes: expected value and the effort to deliver it. High value and low effort goes first. High value and high effort needs careful sequencing. Low value and high effort is where good portfolios go to die. This model is fast and intuitive, which makes it ideal for a first pass before you invest in detailed scoring.
Cost of delay
Cost of delay asks a sharper question: what does it cost us, per week, to not have this finished? Work where the value evaporates if it ships late, such as a compliance deadline or a seasonal launch, scores high. Cost of delay is the model that best counters the bias toward whatever is easy, because it surfaces the expensive consequence of waiting.
Score against capacity, not in a vacuum
The most common prioritization failure is ranking projects as if you could do all of them. You cannot. A ranked list only becomes a portfolio when you draw a line at the capacity you actually have and accept that everything below the line waits. That requires knowing your real capacity, which is its own discipline. We cover it in resource and capacity planning for project portfolios.
Make the tradeoffs visible in governance
A scoring model produces a ranking. It does not make the decision. The decision happens in a governance forum where leaders look at the ranked list, the capacity line, and the projects that fall below it, and consciously choose. The point of the model is to make that choice honest and repeatable rather than political. For how to run that forum, see project portfolio governance.
Re-score on a cadence, not once
Priorities are not set in January and forgotten. New work arrives, assumptions break, and a project that scored well in Q1 may be overtaken by Q3. Re-scoring the portfolio on a regular cadence, even lightly, keeps the ranking honest and gives you a defensible reason to pause or stop work that has slipped. This connects directly to how a project management office earns its keep: not by tracking tasks, but by continuously steering capacity toward the highest-value work.