Project Prioritization

Prioritize projects against strategy, value, risk and capacity

Score candidate and in-flight projects against criteria your organization set in advance, rank them with the method the decision deserves, and carry the result into the funding conversation instead of arguing it there.

The ranking is stored on the projects themselves. Six months later you can still see what was scored, on what basis, and what came out.

Three ranking methods, one definition of value, and a capacity check before anyone commits to a date.

MoSCoW prioritisation of projects in PPM Express

The problem

Ranking is easy. Defending the ranking is the hard part.

Every project on the list has a sponsor who can explain why it matters, a business case that clears the bar, and a date that has already been mentioned to somebody. Lined up side by side, they all look necessary.

So the order gets set by whoever presented last, or loudest, or most senior. Projects below the line are rarely declined outright; they are deferred, carried forward, and argued again from the beginning next quarter.

Use the method the decision deserves

A weighted scoring model when the outcome has to stand up to a board. Four MoSCoW buckets with columns that total budget and benefits when you need a fast call with the money in view. A quick ICE score when you are triaging a long list and precision would be false comfort.

Run two of them across the same portfolio and look at where they disagree. That gap is usually the conversation worth having.

Portfolio prioritisation in PPM Express ranking projects by weighted score

Three methods

Project ranking table in PPM Express showing weighted scores and the funding cut-off line

What a score means

Make the numbers mean the same thing to everyone

Strategic factors and risk factors, each weighted, each with a published value range so a 4 is defined rather than felt. Every project comes out with a Strategic Score and a Risk Score on the same scale.

Budget, forecast, benefits and impact sit on the project record next to the scores, so the ranking conversation happens in money rather than in adjectives. A model already scoring live projects has to be cloned before it can change, which stops anyone redefining value halfway through a cycle.

A ranking you can actually staff

An agreed order is not a plan until somebody checks whether the people exist. Test the ranked portfolio against free capacity, what is left after the commitments your teams already carry, and see the over-allocation while it is still a proposal.
When the order settles, every project is stamped with the outcome, the numbers are baselined at that moment, and the history is kept. Six months on, why a project sat where it sat is a lookup rather than an argument.

PPM Express resource planning view showing planned versus available capacity by person across the portfolio

From ranking to decision

Learn More

Idea Prioritization

Weighted Prioritization Model for selecting right investment

Integrations

Resource capacity planning and utilization

Capacity from real work weeks, so over-allocation surfaces before you commit.

Product

What-If Scenario Planning

Structured Approach for prioritizing and aligning portfolios with strategic priorities and resource constraints

Product

Last updated 20 August 2026

What changes once the model is in place

The order survives the meeting

Agreeing the criteria before the projects are scored means the discussion is about weights, not about whose project it is. Nobody relitigates the basis of the decision every cycle.

Below the line has a reason

A project that misses the cut still has a score, a rank and a recorded rationale. Sponsors argue with the weighting, which is a conversation you can have, rather than with the outcome.

Money and people in the same view

Budget, forecast and benefits on one axis, free capacity on the other. The portfolio you approve is one the organization can pay for and staff.