Most teams argue about scoring methods when the real problem is upstream. Whether you use a weighted matrix, RICE, or a simple ranking, the output is only as good as the criteria you feed it. Choose the wrong factors, or weight the comfortable ones too heavily, and a flawless model still puts the wrong projects at the top of the list. Getting the criteria right is the part of prioritization that actually changes which projects live, and it is the part most portfolios skip.
Key takeaways
- Prioritization criteria are the factors you score every project against. They matter more than the scoring method: bad criteria plus a great model still ranks the wrong work first.
- Most portfolios need five to seven criteria across four groups: strategic value, financial return, risk, and cost or resource demand. More than seven adds noise, not signal.
- Weight the criteria to reflect real strategy, then keep the weights fixed across projects. Changing weights per project is how people rig the ranking.
- Score on a defined 1 to 5 scale with written anchors for each level, so a 4 means the same thing to every scorer.
- Review the criteria set once a year. When strategy shifts, the criteria and their weights should shift with it, not the individual scores.
What are project prioritization criteria?
Project prioritization criteria are the specific factors a portfolio uses to compare projects against each other and decide which ones get funded, staffed, and sequenced first. Instead of ranking projects on gut feel or whoever argues loudest, you agree on a handful of dimensions that actually matter, such as strategic fit, financial return, risk, and resource demand, and you score every project against the same set. These criteria are what the benefit-measurement project selection methods plug into when they decide which candidates qualify for funding in the first place.
The criteria are the inputs; the scoring method is the machine that turns them into a ranked list. People conflate the two, but they are separate decisions. You can run the same criteria through a weighted matrix, a bubble chart, or a formal model and get a similar answer. Run the wrong criteria through any of them and you get a confident, precise, wrong answer. That is why the criteria deserve more debate than the math, and usually get less.
The standard project prioritization criteria, with examples
Across most portfolios, useful criteria cluster into four groups. You do not need every criterion below; you need a handful that fit how your organization actually creates value. Here are the common ones with concrete examples of what a high score looks like.
| Group | Criterion | What it measures | Example of a high score |
|---|---|---|---|
| Strategic value | Strategic alignment | How directly the project advances a stated goal for the year | Project is named in the annual plan as a core initiative |
| Strategic value | Customer or market impact | Effect on retention, acquisition, or a key customer commitment | Unblocks a top-ten account or a contractual obligation |
| Financial return | Expected ROI or revenue | Net financial benefit over a defined horizon | Clear, credible payback inside twelve months |
| Financial return | Cost reduction | Ongoing operating cost the project removes | Retires a recurring expense or manual process |
| Risk | Delivery risk | Likelihood the project fails to deliver as scoped | Proven approach, known team, few dependencies (low risk scores high) |
| Risk | Risk of not doing it | Cost of inaction: compliance, security, or competitive exposure | Missing a regulatory deadline if the project slips |
| Cost and resources | Resource demand | How much of a scarce role or skill the project consumes | Needs little of the constrained team (low demand scores high) |
| Cost and resources | Time to value | How soon benefits start landing | Delivers a usable increment within a quarter |
Notice that two criteria, delivery risk and resource demand, are inverted: a project that is low risk or low demand should score high, because that is the desirable end. Decide the direction of every criterion before you score anything, or your ranking will quietly reward the wrong extreme.
How many criteria should you use?
Five to seven criteria is the practical sweet spot for most portfolios. Fewer than four and you cannot distinguish a strategically vital project from a merely profitable one. More than seven and the extra criteria either duplicate ones you already have or carry so little weight they never change the ranking, while they do add real effort to every scoring cycle. If you find yourself with ten criteria, look for pairs that always move together and merge them.
A common mistake is adding a criterion for every stakeholder who wants their concern represented. That is how a scoring model bloats into a form nobody fills in honestly. Keep the set small enough that scoring a project takes minutes, not an afternoon, and cover the strategic, financial, risk, and cost dimensions rather than a long tail of pet factors.
How to weight prioritization criteria
Not every criterion matters equally, and weighting is where you encode that. Assign each criterion a percentage of the total score so the weights sum to 100. The weights are a direct statement of strategy: a growth-stage company might put 30 percent on strategic alignment and 25 percent on revenue, while a company under cost pressure flips that toward cost reduction and low resource demand.
Here is a worked example using a 1 to 5 score per criterion, then multiplying by weight.
| Criterion | Weight | Project A raw (1 to 5) | Project A weighted | Project B raw (1 to 5) | Project B weighted |
|---|---|---|---|---|---|
| Strategic alignment | 30% | 5 | 1.50 | 2 | 0.60 |
| Financial return | 25% | 3 | 0.75 | 5 | 1.25 |
| Risk of not doing it | 20% | 4 | 0.80 | 2 | 0.40 |
| Low delivery risk | 15% | 3 | 0.45 | 4 | 0.60 |
| Low resource demand | 10% | 2 | 0.20 | 4 | 0.40 |
| Total | 100% | 3.70 | 3.25 |
Project B has the stronger financial return, but Project A wins because it is far more aligned with strategy and more costly to skip, and strategy carries the heaviest weight. That is the weighting doing its job: turning a subjective "which feels more important" into a defensible number. The mechanics of running this at scale sit in your project scoring model, and the side-by-side view executives actually look at is the project prioritization matrix.
Score on a defined scale, not a feeling
A criterion is only useful if two people scoring the same project land close to the same number. Use a 1 to 5 scale and write a short anchor for each level so the numbers mean something. For strategic alignment, a 5 might be "named in the annual plan," a 3 "supports a plan goal indirectly," and a 1 "no line of sight to any stated goal." Anchored scales are the difference between a model that produces consistent rankings and one where every scorer invents their own definition of a 4.
Keep the anchors written down next to the criteria. When a new project owner scores their first project, they should be able to read what each level means rather than guess, and when two scores disagree wildly you have a shared reference to resolve it against.
Where prioritization criteria go wrong
The most common failure is letting the weights move to fit a favored project. Someone wants their initiative on top, so the meeting quietly decides financial return should count for more this quarter. Once weights bend per project, the model is theater. Fix the weights, revisit them only on a deliberate annual cadence, and change scores as facts change, never the weights to change the answer.
The second failure is scoring everything against criteria but never against capacity. A project can score brilliantly and still be undeliverable because the one team it needs is already fully committed. Criteria rank desirability; they do not check feasibility. Pair the ranking with a hard look at resource and capacity planning so the top of your list is work you can actually staff, not just work you wish you could.
The third is treating the criteria as permanent. Strategy changes, and criteria that made sense during a growth push can quietly misdirect the portfolio during a cost-cutting year. Review the criteria set and its weights once a year as part of the broader portfolio prioritization process, and inside the governance forum where these decisions actually stick, described in portfolio governance.
Frequently asked questions
What are project prioritization criteria?
Project prioritization criteria are the factors a portfolio scores every project against to decide funding and sequence, typically strategic alignment, financial return, risk, and resource demand. Instead of ranking projects on gut feel, you agree on a handful of dimensions that matter and score all projects on the same set. The criteria are the inputs; the scoring method turns them into a ranked list.
What are examples of project prioritization criteria?
Common examples include strategic alignment, expected ROI or revenue, cost reduction, customer or market impact, delivery risk, the risk of not doing the project, resource demand on scarce roles, and time to value. Most portfolios pick five to seven of these across four groups: strategic value, financial return, risk, and cost or resources. The right set depends on how your organization actually creates value.
How do you weight project prioritization criteria?
Assign each criterion a percentage of the total score so the weights sum to 100, reflecting real strategy: a growth company weights strategic alignment and revenue heavily, a cost-focused one weights cost reduction and low resource demand. Score each project 1 to 5 per criterion, multiply by the weight, and sum for a total. Keep the weights fixed across projects so the ranking stays honest.
How many prioritization criteria should you use?
Five to seven criteria works for most portfolios. Fewer than four cannot separate a strategically vital project from a merely profitable one, while more than seven usually duplicate existing criteria or carry too little weight to change the ranking. If you end up with ten, merge the pairs that always move together and keep the set small enough that scoring a project takes minutes.
What is the difference between prioritization criteria and a scoring model?
Prioritization criteria are the factors you evaluate, such as strategic fit and risk; the scoring model is the method that combines them into a ranked list, such as a weighted matrix or RICE. The criteria decide what you measure; the model decides how you turn those measurements into an order. Good criteria matter more, because the wrong factors produce a confident but wrong ranking through any model.