Project Prioritization: The Ultimate Guide for PMOs

#What is Project Prioritization?

Project prioritization is how organizations decide which projects to start, stop, delay, or accelerate when resources are limited, and plays a critical role in connecting the goals of the organization to the outcomes delivered by the PMO.

Done well, it turns strategy into a focused, deliverable portfolio.
Done badly, it creates the familiar PMO nightmare: too many projects, overloaded teams, pet projects, weak business cases, and a roadmap nobody truly believes in.

The right approach is simple to explain but takes work to deliver:

Project Prioritization = Value + Constraints + Buy-In

• Value → What does the project contribute to our business goals?
• Constraints → How can we maximize contribution while staying within constraints?
• Buy-In → Will stakeholders support the decision?

The key is to cover all angles: miss one, and the system breaks:

• Value without constraints → A wish list
• Constraints without value → Efficient delivery of the wrong work
• No buy-in → Decisions that get ignored, constantly changing priorities, pet projects and overloaded teams

This guide will show you how a value-focused PMO can develop all three elements, and in doing so unlock the massive upside of a well-aligned portfolio.

💡Pro Tip: Next, we'll dig deep to explain why prioritization is critical, and why there's a right way to fix it. If you're already ready to get started you can jump straight to our 10-Step PMO implementation guide now.

#What this guide covers

This is a complete guide to project prioritization for PMOs, but if you want to jump ahead here are the topics we cover:

• What is Project Prioritization?
• Why Project Prioritization matters
• Who owns Project Prioritization?
• Common Project Prioritization challenges
• Project Prioritization methods and frameworks
• How to prioritize projects: 10-step PMO process
• Project Prioritization example
• Project Prioritization Matrix and other visualisations
• Best Practices and common mistakes
• Case Studies
• How to build a Case for Change
• Free templates and downloads
• Project Prioritization software
• FAQs
• Final thought: Time to fix your strategy to delivery gap

👉 Busy right now but want to learn more? Download the Free E-Book

#Why Project Prioritization matters

Project prioritization is not just governance. It is one of the most direct ways to improve the return an organization gets from limited budget, capacity, and leadership attention.

The evidence is hard to ignore:

• Research by the PMI and the Economist Intelligence Unit found that 20% of projects are so badly aligned with the goals of the organization that they should be stopped.
  📖 Source: PMI / Economist Intelligence Unit - Implementing the Project Portfolio: A Vital C‑Suite Focus
• PMI reported that poor project selection wastes an average of US$97 million for every US$1 billion invested in projects and programs.
  📖 Source: PMI – Pulse of the Profession
• Organizations with enterprise PMOs aligned to strategy report 38% more projects meeting original goals and business intent and 33% fewer project failures.
  📖 Source: PMI – Strategic Alignment Report
• McKinsey found that companies actively reallocating resources toward stronger opportunities were worth 40% more after 15 years than less dynamic peers.
  📖 Source: McKinsey - Put your money where your strategy is
• APA’s review of task-switching research notes that multitasking can take more time and create more errors, with switching costs reaching as much as 40% of productive time – unlocking a productivity upside to a more focused team.
  📖 Source: American Psychological Association (APA)
• HBR research found that process-management approaches that include limiting work in progress and relieving bottlenecks reduced product-development times by 30% to 50%, reflecting the speed-to-value upside of prioritization.
  📖 Source: HBR: Getting the Most out of Your Product Development Process

The message is simple: you do not lose most value in delivery. You lose it in selection.

When low-value projects enter the portfolio, bottlenecked teams get overloaded, high-value work waits, and delivery performance suffers. Better prioritization helps the PMO stop that value leakage before it starts.

👉 Find out why PMOs should love prioritization with renowned PMO expert, Laura Barnard

#Key Takeaways

We’ll cover a broad sweep of the topic in this guide, but here are the main points we’ll zoom in on:

• Project Prioritization drives ROI. By cutting poorly aligned work and staggering projects to reduce the volume of work-in-progress you can step-change returns.
• Project Prioritization requires collaboration. Decision authority sits with leadership, but the PMO can play an invaluable role shaping the process.
• Project Prioritization is not just ranking. It is a capability, an organizational muscle that the PMO must build to support better executive decision making.
• Good criteria define value. Once value is clear, decisions become consistent and defensible. They’re the basis for data-led planning and clear alignment.
• Quantification means better decisions. If projects are scored, selection becomes mathematical and objective, not a negotiated settlement.
• Complex portfolios need multi-criteria approaches. Simpler models are available for narrow use cases, but do not scale effectively.
• Weighted scoring is the baseline; AHP makes it stronger. AHP adds decision-science rigour by strengthening trade-offs, consistency and alignment. That’s why it’s proven to be more effective with prioritizing portfolios.
• Capacity shapes the decision. “Should we do it?” and “Can we do it?” are different questions. Combine them for the best results.
• Buy-in is critical. If leaders don’t trust the model, prioritization collapses into politics. If teams don’t engage with the process, you don’t get quality data.

This guide has been developed through extensive client work, research into what works and collaboration with the sector’s leading experts.

We want to share what we’ve learned to help people, because ultimately effective prioritization is good for everyone.

👉 Want to find out what that could mean for you? Book your Free Portfolio Briefing

#Who Owns Project Prioritization?

Many organizations struggle with this question because there is no universal answer. Project prioritization sits across strategy, funding, delivery and governance, which means no single function has the full picture or accountability.

• PMO: Usually facilitates the process, manages intake, coordinates scoring, and turns project data into decision-ready recommendations.
  
  The challenge is that many PMOs are asked to administer prioritization without being given authority to say “no” or challenge demand.
  
  
• Finance: Owns budget discipline and validates investment logic.
  
  Finance can assess funding, costs and business cases, but often has limited visibility of resource capacity, delivery constraints and cross-functional bottlenecks.
  
  
• Strategy / Transformation: Champions strategic programmes and helps define what matters most.
  
  However, strategy teams do not usually control operational resources, so they will push priorities without owning the full trade-off across the portfolio.
  
  
• Delivery Teams: Understand capacity, dependencies and feasibility better than anyone.
  
  But delivery teams usually operate within functional boundaries, so local prioritization can create conflicts when work crosses departments.

The practical answer is this:

Leadership owns the trade-offs. The PMO owns the process. Strategy owns major cross-functional initiatives. Delivery owns the resource requirements. In other words, only structured collaboration can make prioritization work.

That is the PMO opportunity: not to seize control, but to help all the teams to make better choices with clearer data, better visibility and a repeatable way to revisit decisions as priorities change.

PMOs are also perfectly placed to champion the methodology and tooling needed to support this collaboration, but if you’re reading this with either a Strategy or Finance hat on, then you are equally capable of being that driving force.

And that’s exactly what we aim to deliver in this guide: an in-depth run through of the right way to prioritize projects and introduction to the tooling that makes it straightforward to achieve.

💡Pro Tip: Boost Buy-In by involving people in building your prioritization solution. Ideally a senior sponsor, plus representatives from Delivery, Strategy, Finance and the PMO.

#Common Project Prioritization Challenges: 7 Signs Your Process Is Broken

For much of this guide we’ll focus on what works.

However, most clients start with what does not work, so let’s use that as our jumping off point – common prioritization challenges.

Below are seven common signs of a broken prioritization process. Some are symptoms of demand overload; others are symptoms of weak selection, poor intake, or ignored capacity. Together, they point to the same root cause: the organization lacks a reliable way to decide which work matters most.

By understanding these drivers, you can help your organization recognize four key facts:

• Your frustrations are common, not an intractable mystery.
• Your challenges are solvable, but you need to develop a sustainable solution.
• Poor prioritization is the capability gap behind multiple operational failings.
• Don’t get stuck responding to problems, fix the underlying causes.

If you find yourself nodding in agreement you are in the right place. These are the problems we help clients to solve.

💡Pro Tip: Start documenting your prioritization challenges, along with the evidence that demonstrates their impact on the business. It’s key to getting leadership to buy into the need to change.

#1. There are Too Many Projects

If you have a bloated backlog, with delivery teams spread too thinly, and projects taking too long to complete then you have a problem with Too Many Projects.

Too Many Projects is often seen as a resource problem.

The most in-demand people are the pressure points where overload bites. But before you reach for the contractor requisition form you should always ask if this problem could be solved through better prioritization instead.

"Hire" might be an easier conversation, but it's not always the right one for your ROI.

Too Many Projects is also often flagged as a delivery cadence issue.

When you say it will take eighteen months and the stakeholder looks indignant, Too Many Projects is often the cause. If critical resources are spread thinly, the timeline of a project is not just how long it takes to do the work; you have to add on how long it takes to get the resource you need, when that person is already over-committed on existing projects.

This is why having fewer projects in flight means initiatives complete faster.

That's called project prioritization.

#2. Everything Is Priority 1

One client had 80% of their projects flagged as Priority 1. Then we evaluated the portfolio and found that 30% of the portfolio was obsolete.

So not priority one, then.

As that client said, “If everything is priority 1, nothing is priority 1.”

Priority inflation is what happens when leadership wants focus without trade-offs. It feels easier to label everything important than to have the uncomfortable conversation about what should wait.

After all, everything is Priority 1 to someone.

Unfortunately, delivery teams cannot execute ambiguity, so will typically pick the projects they like the best, or follow the route of least resistance, with executive frustration or a mounting technical-debt as equally likely outcomes.

#3. The Loudest Voice Wins

The “Loudest Voice” model is brutally common.

It may be the most senior sponsor, the most persistent department head, or the person who can write the most well-framed business case. It might be the director that knows how to game the system.

But what they are not is all-knowing. They have blind spots and biases that make their point-of-view dangerous. Why? Because they're human; we all have these flaws. It's why effective prioritization needs to be collaborative, harnessing the judgements of multiple stakeholders, without making the process overly cumbersome.

One watch out: the awkward truth is that the loudest voice often has the most to lose from a better process. If prioritization becomes transparent, influence must be shared. That is why buy-in really matters.

#4. No Shared Definition of Value

“Strategic alignment” sounds sensible until everyone claims it.

The CEO’s growth initiative is strategic. The CFO’s efficiency program is strategic. The compliance project is strategic. The operational improvement is strategic. The pet project is, apparently, deeply strategic.

Without agreed criteria, strategy becomes a label rather than a decision rule. This is especially true if that alignment is scored by a yes-no field that makes no effort to distinguish a game-changing project from marginally relevant work.

The same often happens with “mandatory”, when an ill-defined threat of regulatory pressure is used to circumvent a review process that stakeholders don’t buy into.

Like “Priority 1”, if everything is “strategic” then nothing is strategic.

#5. Weak Demand Management and Intake Controls

If your intake process is weak, prioritization will fail.

You must collect enough information to compare projects fairly: what the project is, why it matters, what it contributes to corporate goals, what it costs, what capacity it consumes, what risks it creates or reduces, and what happens if you do nothing.

It also needs decision authority. The ability to reject, to demand a better business case, to ask for a version that takes out the padding.

It is this actionability which stops Intake being admin-tax and gives the PMO a route to demonstrate its value to leadership.

Another way to frame this is that Demand Management needs to be a funnel, filtering out weaker candidates, rather than a tunnel, where all projects pass, thus rendering the hurdles as pointless.

#6. Selection is not constrained by Delivery Capacity

A ranked list does not tell you whether the portfolio is deliverable.

For that, it’s imperative that you can scale projects. The lowest level requirement would be cost, even if it’s just a T-Shirt Estimate.

But quality prioritization demands more, adding in a high-level view of the resource needed to deliver the work. This is not a detailed plan: it’s simply a best-estimate view on what’s needed to get the job done.

This is critical, because we can use it for Capacity Planning, specifically to identify the risk of bottlenecks, so we can avoid overloading our most in-demand teams. Ignoring this risk at a planning stage is often the root cause of ‘delivery’ problems, that manifest as those teams struggle to operate at >100%.

This is why capacity planning belongs inside prioritization, not after it. A ranked list tells you what looks valuable; capacity data tells you which projects you can select, versus which must wait for resources to become available.

#7. Zombie Projects and Pet Projects

If a portfolio lacks a mechanism for controlling prioritization it usually ends up with weak projects that everyone knows are not worthwhile. This is bad for portfolio ROI, PMO credibility and the morale of the teams who are working on these projects.

Pet Projects are the poorly aligned, ill-conceived ‘bright ideas’ that the Loudest Voice believed were worthwhile. Once agreed they tend to be protected but will struggle to show value due to a weak business case.

Zombie Projects were once probably worthwhile. But now costs have gone up, benefits slipped and timelines stretched. The problem is that nobody wants to take responsibility for explaining this to leadership, and there is no process to call out the issue.

Meanwhile strong new projects grow old waiting for resource.

#Do you have a prioritization problem?

If this sounds familiar you have a prioritization problem.

Not a communication problem, a project governance problem, a delivery problem or a resource problem.

These are the symptoms which flow out of a fundamental failure to select the right projects effectively.

The first step to solving prioritization is to build awareness of the problem. After all, if leadership just hear “late”, “over budget” and “at risk” their first thought will not be “fix prioritization”.

👉 To help you with this process we’ve prepared this fun view of the Top 10 Signs you have a Prioritization Problem. Download, share and start the conversation.

So, the next challenge: what methodology should we use to solve your prioritization problem?

#Project Prioritization Methods and Frameworks Compared

There is no shortage of project prioritization methods. But most are not right for portfolio selection.

Methods are designed for specific use cases; task lists, product backlogs, or financial analysis. When applied to portfolios, they come up short.

The reason comes back to our Prioritization definition:

Value + Constraints + Buy-In.

Most methods optimize for one dimension, not all three, with only one approach, the Weighted Scoring Model (sometimes called Multi-criteria Decision Analysis or MCDA), delivering what’s needed.

And it’s also important to build that model well, and for this we’ll explore the power of Decision Science, specifically AHP, The Analytic Hierarchy Process, as the best way to solve project prioritization.

#Project Prioritization Methods at a Glance

#What These Methods Actually Do

These models are common ways to prioritize that add analytical rigour to simply following the loudest voice, or getting round a table with Post-it notes:

• MoSCoW (Must have, Should have, Could have, Won’t have): categorize priorities based on a shared view of their importance. Working out what goes where is subjective, but it's simple and creates actionable differentiation.
• Eisenhower Matrix: Splits work into urgent vs important, which is useful for short-term task prioritization, but highly subjective if you need to compare projects from multiple stakeholders, all of whom think their requests are both.
• RICE (Reach, Impact, Confidence, Effort): Scores initiatives based on how many people they affect, how much impact they have, confidence in the estimate, and effort required. Useful for product features and more objective, but falls apart if projects are in any way diverse or complex.
• WSJF (Weighted Shortest Job First): Prioritizes work by comparing cost of delay vs job duration, favouring high-value, quick-to-deliver work. Ignores non-financial business factors which, in project portfolios, is usually too narrow. Mostly used to prioritize simple, Agile backlogs. 
• Financial models (ROI, NPV, Payback etc): Translates outcomes into monetary value, enabling direct comparison, but only for financial benefits. Once again, other drivers of business value are ignored.

These approaches are not suitable for project prioritization. They are great for prioritizing product backlogs, and managing task lists, and if this is your goal there are great resources available elsewhere that go deeper on these methodologies.

Let’s explore why in a little more detail, so we can then go on to show what we need to do the job properly.

#Simple methods are not enough for Portfolio Prioritization

Most methods follow this pattern:

Reduce complexity → rank options → move forward

This works well when:

• Decisions are local
• Stakeholders are aligned
• Trade-offs are simple

That is why methods like MoSCoW, RICE, and Eisenhower work well for:

• Start-up teams
• Agile backlogs
• Small decision sets

But portfolio prioritization is different. To understand why, let’s go back to our three-dimensions:

"Value" is not a simple definition. It’s a series of trade-offs:

• Revenue vs risk
• Growth vs efficiency
• Innovation vs maintenance

These trade-offs are complex judgements. That's why senior stakeholders will disagree with each other, with the process of finding balance a key part of effective prioritization.

Neither are they standard.

Criteria must be tailored to every organisation and every portfolio to reflect strategy. Generic criteria never build the trust needed to give a model the decision authority needed to drive change.

Simple ranking cannot integrate with capacity data:

Listing work in priority order is fine if the tasks are roughly the same size. In most portfolios this is not the case. There are quick wins, there are larger scale investments. The effort required to deliver the work must be part of the review process so that value-for-money (or effort) can be used as a determinate for selection.

And that's just applying a financial constraint. The same "value for" logic needs to apply for your most bottlenecked resources too.

Oversimplification does not build buy-in:

When project scores are captured as fields like “Must-Have”, “Impact” and “Importance” they offer no rationale to explain why a project scores well or poorly. The category that a project lands in is often driven by politics and our old friend, the Loudest Voice.

That means when results are published there is no trust, given that they are inherently so reliant on the opaque judgement of the people scoring.

This level of transparency is key for buy-in. It builds trust that the process is both rigorous and fair.

💡Pro Tip: Watch out for the colleague trying to promote a product prioritization framework for portfolio prioritization problem. It sounds clever but rarely works.

#Why ROI Is Useful, But Not Enough

Financial models such as ROI, NPV, and payback form a key part of most business cases.
Here’s how they work:

• ROI (Return on Investment): Measures how much value a project is expected to generate compared to its cost.
  
  Useful for comparing investments, but can overlook strategic, operational, or risk-related benefits.
  
  
• NPV (Net Present Value): Calculates the value of future benefits in today's money by accounting for the time value of money.
  
  Helps compare projects with different timelines but depends heavily on forecasting assumptions especially the growth rate in perpetuity. So not quite the Loudest Voice, but instead the most optimistic set of long term projections.
  
  
• Payback Period: Measures how long it takes for a project to recover its initial investment. 
  
  Simple and intuitive but ignores benefits delivered after the payback point and may favour short-term wins over long-term value.

They all make sense when applied to major investments, with finance needing to show due diligence in how they spend the company’s funds.

However, they are limited as the sole source of prioritization:

• No consideration for strategy, fit, risk or any other criteria other than financial.
• Reliant on the underlying business case, making spreadsheet-based optimism a key determinant in the outcome of a review.
• Struggle with investments where the time-horizon differs, with a tendency to favour shorter term projects.

That is why financial metrics should be part of the model, but not the model itself.

💡Pro Tip: Always find out which financial KPIs are already being used to assess projects. Is this a gap to plug or a collaboration to integrate into a balanced scoring model?

#Why Weighted Scoring Is the Best Approach

Weighted scoring models solve a key problem:

How do you compare different types of Value?

They do this by breaking the question into underlying elements:

• Defining criteria (what matters)
• Assigning weights (what matters most)
• Scoring projects consistently (against criteria)

This allows you to compare:

• Financial value
• Strategic alignment
• Risk
• Stakeholder impact
• …anything else that represents a reason to invest for leadership

The output is a score that represents each project's contribution to your business goals. This means it’s perfect for working out Value for Money, which is a more meaningful and well-rounded selection metric than ranking:

Value Score / Cost of Project = Value for Money

We’ll explore how to use this in Data Visualization below, but the point is simple: this is a far more nuanced metric with which to build a cost-constrained portfolio.

Finally, the process of building this model helps build Buy-In. The criteria and the weights are defined by senior stakeholders, forcing them to explore disagreements and align on a shared outcome.

Project scoring can come from another model, a panel of experts or a conversation between stakeholders. But the point is that the assessment is modular, focusing on a series of specific questions - to what extent will this project support strategy / risk / ROI - rather than "is this project good?"

People may not like the answers, but their provenance is hard to debate.

That’s why a Weighted Scoring Model is the best approach for Portfolio. But for a sustainable solution it’s only half the answer.

#Where Weighted Scoring Breaks

Many organizations stop at the Weighted Model and run into problems:

• Weights are guessed or politically negotiated
• Criteria are vague or overlapping
• Scoring is inconsistent and often made at too high of a level
• Stakeholders do not trust the output if it challenges their preconceptions

At that point, the model becomes a spreadsheet version of the Loudest Voice.

More work, more data, but often not more impactful.

But there is a better way: The Analytic Hierarchy Process (AHP) leverages Decision Science to produce more robust results.

Let’s explore why next.

#Why AHP Is Better for Portfolios

AHP (Analytic Hierarchy Process) improves weighted scoring by fixing its weakest point: how weights are created.

Instead of guessing percentages, AHP uses pairwise comparison which asks users to judge the relative importance of competing criteria:

• Which criterion matters more?
• By how much?

This creates a mathematically derived weight set that reflects leadership priorities rather than spreadsheet politics. This is supported by consistency scoring, a mathematical formula that measures the consistency of pairwise judgements.

Pairwise also better aligned to how humans express judgement. Relative preferences are proven as a better way to quantify importance than plucking a number out of the air.

That’s not all.

AHP also addresses common pitfalls that undermine the weighted model in your spreadsheet:

• Model building methodology that reduces ambiguity, duplication and other common errors that quietly undermine a weighted model.
• Structured sub-criteria modelling to add detailed measurement to broad ambiguous high-level goals (this is the “H” in AHP).
• Normalized project scoring that works equally well with qualitative scales or “hard” data like a financial model output.
• Iterative data collection that reduces anchoring and bias by combining survey and workshop formats.

Put together, it’s simply the most effective way to turn stakeholder judgements into a scalable model. We explore AHP in more detail in our Ten Steps guide below, but at this point it is worth asking a simple question:

If you know you need a weighted scoring model, why stop halfway when a few extra steps can give you a far stronger foundation?

If you’re struggling with project prioritization, you’re not the first.

Don’t re-invent the wheel when Decision Science has already worked out the best way to solve the problem.

#The Best Model for Prioritization: Conclusion

At portfolio level, prioritization must answer three questions:

• Value → Can I accurately reflect a projects’ contribution to my business goals?
• Constraints → Do I get a quantifiable output (a score) I can use for modelling and determining “value for money”?
• Buy-In → Will stakeholders support the decision?

Most methods only answer one or two of these:

If your method cannot handle all three it cannot deliver the clarity of outcome you need to support effective decision making.

That’s why the only way to solve all three dimensions is a weighted model, powered by AHP.

#AHP – Go Deeper

If you'd like to learn more about AHP and why there is no better way to prioritize projects, we recommend:

• Read Ricardo Vargas from the PMI, on why this is the best way to prioritize.
• Learn how AHP is used by NASA with best-selling author, Dr James Brown.
• Dive into the academic research including this study from the University of New South Wales, which identified AHP as the best model for Portfolio Prioritization
• Read our Ultimate Guide to AHP, where we explore its origins and the math that makes it so effective.
• Dive into our Blog that goes deeper into Why Prioritization needs AHP.

The key point is that it’s simple, practical and accessible for any PMO.

With the right tooling it’s no more effort than a spreadsheet-based weighted scoring model, and provides a far more durable base from which to develop project prioritization as a PMO capability.

Let’s learn how next.

#How to Prioritize Projects: A 10-Step PMO Process

The easiest way to prioritize is to get into a room with a whiteboard and Post-its. However, if that’s not worked so far, it may be time to invest in a better prioritization approach.

The following steps are a combination of what the decision science shows and what we’ve learned implementing prioritization for complex organizations around the world over more than a decade.

This is what we do. This is our house. Come on in and make yourself comfortable!

👉 If you would like to discuss how effective prioritization can support your portfolio then book your free Portfolio Briefing.

#Step 1 - Identify Project Prioritization Criteria

A credible model does not try to capture everything.

It captures the right things, clearly enough to support real decisions.

At a minimum, you should consider including these six dimensions of value:

This is not a checklist – yes or no – but a series of questions where we need to build measurable indications of which projects will contribute the most.

The goal is to ensure that we consider the main lenses through which decision makers in leadership will assess projects.

In this sense the simplest place to start is by asking, "What does your CFO / COO / CEO always look for in a project review?” Those are your criteria, hiding in plain sight as the things that different members of the leadership team think are important.

Or ask, “What are the pros and cons of projects we are working on now?” They can be a signpost to criteria that really matter.

Don’t try to be too clever: use existing business language and relatable examples: after all our goal in the PMO is to build buy-in for our model, not to try and force yet another framework onto stakeholders.

Always prioritize Buy-In ahead of technical detail because the number one objective is leadership engagement. Without it the model has no value.

If you want to explore potential criteria for your portfolio, we can help. Start here with our free e-book:

👉 Download our Free 80-Criteria Guide for more tips on how to build an AHP model

#Step 2 - Build a Project Prioritization Model

There are some very simple technical elements to a good AHP model that will greatly improve its effectiveness.

Here are the main ones:

• Size Matters. The common failure mode is not missing criteria. It’s having too many, just pushing everyone’s ideas into Frankenstein’s model. Every extra criterion adds work for scoring and with it increases the risk of losing buy-in.
  
  We recommend five criteria – plus or minus two – as a practical balance between model granularity and usability.
  
  
• Add precision with “H” – Hierarchy. Five criteria, each with 3 sub-criteria can deliver the balance of a simple model with the analytical rigour needed to differentiate key investments from marginal opportunities.
  
  The criteria might be a broad “deliver the strategy”, but the sub-criteria used for scoring will demand greater rigour: which of the key levers will this project impact, and to what extent?
  
  
• Ambiguity is your enemy, and nothing is worse for it than an "AND" in your sub-criteria.
  
  For example, you have a sub-criterion that contains X and Y. How can you then compare a project that’s great for X, poor for Y vs. one that is OK for both? Answer? You cannot. X and Y should be separate sub-criteria.

• Keep criteria mutually exclusive, otherwise your pairwise won't make sense. For example, don’t have margin and revenue as cash amounts, as one is derivative of the other. Either pick the one that really matters or nuance the metric to measure different things.
  
  In this case it would mean using margin rate and revenue, therefore giving leadership the choice between top line growth or underlying profitability: a genuine trade-off.

• Symmetry is best. Aim to have (about) the same number of sub-criteria below each of your top-level criteria. Why? When you create a weight set the value of each Criterion will be shared between its sub-criteria.
  
  That means if one criterion has 10 sub-criteria, all those subs, individually, are likely to have limited impact on total score. Conversely, a branch with two sub-criteria means those subs will be important drivers. This is not a hard rule: but it’s important to bear in mind as you design your model to avoid producing results that don’t reflect intent.

Methodology does matter. Not because AHP models need to be perfect, but because best practice has built up with real-world experience to produce models that work.

💡Pro Tip: Always test your model before formal launch. Does it feel right and produce intuitive outputs? Gut checks matter.

#Step 3 - Weight Criteria, Build Executive Consensus

Once you have good criteria you need to build agreement on their relative importance. Indeed, this is a key point of reason for selecting AHP over simple spreadsheet-based Weighted Scoring Models.

With AHP, we use Pairwise comparison, an exercise where we compare criteria to one another:

Which matters more, and to what extent?

Do this across all criteria and you establish a mathematical relationship between the criteria, i.e. a weighted model.

You also get a consistency score showing the extent to which your answers agreed with each other. This is useful as it acts as a sanity check to iron out the oddities of human judgement.

To understand this calculation you can dig into matrix maths, or follow the rule we use with clients that say a grumpy face means re-check your votes.

Next, iterate until your answers are stable and you have a coherent model.

Have folks do this on their own, then get them together to compare results. It might seem like extra work but we do it for three reasons:

• Weights represent the collective perspective of the leadership group, so you need to factor in everyone's opinion, irrespective of loudness of voice.
• Pooling different perspectives builds quality. Each participant brings their own insight, their own journey and their own biases. Working as a group these add up to a better model.
• Everyone needs to be heard. Involving the wider group builds trust. This buy in is critical for prioritization’s success.

We always get the feedback that this is time well spent, reflecting on goals, prioritizing between outcomes and learning from colleagues.

Moreover, as it usually only needs to happen once a year; that’s a net time-saver.

How?

The decisions that follow are faster with fewer meetings needed to “negotiate” the portfolio. The need to micro-manage project selection is reduced.

💡Pro Tip: Use an external facilitator if you want someone to help steer the conversation with objective focus or if you need someone who can say, “No!” to power without fear of repercussions.

#Step 4 - Set Criteria-level Measurement

The bottom level of the model needs to be used to score projects. For this we must apply measurement.

There are three ways to do this:

• Score with a Scale: Add a series of verbal levels and assign each one a value.
  
  The top level is your benchmark for a perfect project, while everything else is then relative to this. Scales perform a critical transformation function: turning subjective opinions into data points. This quantification is a critical and powerful feature of AHP.
  
  We suggest five simple rules for building effective scales:

1. 1. Always have a zero, so a project can be adjudged to add make no contribution to a criterion.
   2. Have enough levels to differentiate projects, but not so many that scorers are bamboozled. We like a five-tier approach for the right balance.
   3. Add clear descriptions. The test is that two people can read it and conclude the same thing. Avoid meaningless buzzwords.
   4. Use templates but edit. Standard scales in our software and guides give language and framing but tweak them so they align to the specifics of your business.
   5. Quantify levels if you can. Adding specific bandings eliminates ambiguity in scoring. Not always possible but use when applicable.

• Score with benefits data: For financial objectives especially, projects often already have projected benefits for revenue, savings and measurements like NPV.
  
  These are perfect for an AHP model.
  
  Simply define a normalization cap (the value that represents the perfect project) then plug in project values to determine the relative merit of competing investment choices. This approach is great for minimizing effort duplication, and keeping aligned with finance.
  
• Pairwise comparison: This is rarely useful for a portfolio prioritization challenge as it’s ill-suited for a portfolio that changes over time.
  
  However, as a one-off review on a small number of options it can work and is very much the heritage AHP approach you may have learned about back in the day.

💡Pro Tip: Run a test survey before the full launch. Does project level scoring make sense with the scales you’ve chosen?

#Step 5 - Score Projects using the Wisdom of the (Small) Crowd

Next, it’s time to score projects, and here’s how:

• Don’t jump right into “task mode”: Begin with comms to explain the process and the projects.
  
  Remember the importance of building buy-in. Position it using “What’s In It For Me” to show that good prioritization means upside for everyone by reducing noise and growing impact. The people you’ll be asking to score projects are busy, so help them understand that good prioritization means less overload and fewer late nights / missed soccer games!

• Divide and conquer: Spread the work, broaden the participation base. It’s a win-win.
  
  You can break up scoring Assessments by criteria or by project – the point is that you are minimizing the extent to which people are “guessing” when it comes to scoring projects by matching questions to expertise.

• Get people to work as a team: Ideally 3-4 people should be scoring a project, because their collective insight will outperform that of any one of them alone.
  
  There’s Decision Science logic in this approach, inspired by both AHP and Dan Kahneman’s research on “Noise”, but the easiest way to position this is as an exercise in collaboration:
  
  Together we make better decisions.
  
  Quality scoring means we challenge each other’s blind spots and help each other learn to view from complementary perspectives. We seek out knowledge where it is, rather than letting the most opinionated or most biased voice anchor the debate.

Put all these factors together and it means we're building buy-in, making prioritization a transparent Team Sport and not a Black Box mandate.

👉 Daniel Kahneman – Noise: A Flaw in Human Judgment

#Step 6 – Model Launch – test, iterate, communicate

There is a simple way to test whether your model works:

If a project scores highly, would leadership genuinely believe it deserves priority?

If the answer is no, then the model is wrong. Because the model is not there to tell people what they think. It’s there to create a shared framework that everyone trusts as valid, and leadership will not do this until they see it working.

Also prepare clear communications. The process of scoring is new. The criteria may be novel to the people doing the scoring. Don’t assume an email link and a deadline is enough. Make sure it's clear that you value their opinion, as well as asking for their time.

💡Pro Tip: Always take time to test and iterate since trust matters more than milestones.

#Step 7 - Apply Constraints

Our formula for prioritization was more than Value and Buy-In. We also need to factor in Constraints – namely the factors that stop us being able to say yes to everything.

These four are the most common:

• Funding: Without it projects simply cannot happen.
  
  This is where a close working relationship with Finance is important. Budget setting is, in essence, a prioritization process; so why not work together?

• Resource: Most organizations run out of people before they run out of budget. Without people to do the work, plans are not credible.
  
  Without understanding which projects need your most in-demand resources, how can you make prioritization trade-offs? This is especially true when teams cross reporting lines, and silo-based prioritization creates contradictory rankings.

• Time: Urgency can be real. Delivering the Christmas Marketing plan in January is pointless.
  
  Time also matters in setting a planning horizon. How far out can we credibly plan projects before people just hear “never”?

• Dependencies: Recognise that some projects rely on others for shared capabilities, meaning that to access the value from one project may necessitate investment in another.
  
  This may not be easy, as these constraints are not usually directly in the gift of PMO to “control”. However, recognising them in your prioritization process is key to producing a practical outcome that informs quality decision making.

To be clear: this is not about dictating to other teams; it’s about co-ordinating choices around value so leadership can achieve their goals. Often it's also about building capability, to get to the constraint data and forecast data needed (more on this later).

It’s also important to recognise that tackling constraints can go deeper, as factors such as technology, brand and physical spaces limit choices, and prioritization blends into transformation.

👉 Read more about those factors with TransparentChoice partner, and transformation expert Rebecca Reynolds.

#Step 8 - Scenario-Based Planning: Turning Prioritization into Decisions

Once you have scored projects and defined constraints, there is a mathematically optimal portfolio you can select.

But as a PMO this is not your role to do so.

Instead, use it as a Base Case, and then ask, “What If”?

• Swap projects: This could be to improve Strategic Fit (alignment to criteria weights).
  
  It could be to reduce risk. It could be to indulge the “feedback” of a key stakeholder. The point is to make the changes while respecting constraints.

• Add capacity: Unblock key bottlenecks and see what else can get done.
  
  Then work out the supplementary work (or investment) needed to make this credible.

• Switch plan versions: What happens if our top 5 projects are tasked to go harder and end sooner?
  
  Or if we take a high-cost investment and de-specify it?

This is leadership’s plan and giving them control over those choices is another way to build the buy-in needed for success. 

💡Pro Tip: Running a little hot in a resource group can be an acceptable tactical risk. But be sure to treat it as such and work on mitigations for when Murphy’s Law hits your bottleneck.

#Step 9 – Use Value-led Sequencing to Stagger Projects

So far, we’ve focused on Prioritization as a Yes/No decision. In reality, it’s more subtle, and includes a critical third way:

Not yet.

That’s because delaying requests is critical for the PMO. Here’s why:

• Accelerate value: High priority work can move faster to generate the quick(er) wins.
  
  That’s less time for things to go wrong, and faster route to the business benefit that boosts PMO credibility.

• Preserve focus: Teams lose value when they multi-task, spreading time and energy too thinly as they juggle too many Work-In-Progress projects in parallel.
  
  That’s why staggering start dates means teams can finish what they started sooner.

• Boost Resilience: Things go wrong - that’s just Murphy’s Law. If you have teams working on multiple projects in parallel their problems become contagious.
  
  Limiting work-in-progress gives teams the adaptability to protect the flow of work across the portfolio.

• Keep momentum: Proposals marked for prioritization in the future can remain in outline form until they are ready to go.
  
  That means you can use that kick-off energy to get stuck into work, rather than planning, delaying, then re-planning later.
  
  
• Manage expectations: If people know that a project will happen later, they can plan around it. Find interim solutions and set targets accordingly.
  If they get approval, followed by nothing, then the PMO looks ineffective.

The solution is to build “Not Yet” into your scenarios. Instead of forcing every project into “approved” or “rejected,” create a future-start cohort. Leadership can then decide what starts now, what waits for capacity, and what needs to be revisited next quarter.

This provides clarity for everyone, so the costs, benefits and work are clearly planned rather than vaguely hoped for.

👉 Learn more about the power of scheduling with TransparentChoice partner and Theory of Constraints practitioner Mike Hannon

#Step 10 – Create a Baseline, then start Iterating

Once scenarios are locked in, the job is done. The right projects start; everyone feels positive. Just wait for benefits, right?

Not quite.

In fact, not ever.

Because your plan is out of date as soon as it’s agreed. Estimates hardened with detailed planning. Benefit projections shift with market movements. Not to mention an unexpected headcount freeze. Then, there’s a new “must do” project.

This isn’t bad luck: it’s a reality that every PMO will recognise, and it’s important that prioritization is able to iterate to respond.

Not every day, or every week, but somewhere between once a month and once a quarter the plan needs to refresh.

Not a wholesale re-scoring: simply a check in to determine are we still on-track, and is there a better plan that would be worth switching into?

Create a baseline so there’s clarity on what was agreed, then use that reference point to give leadership the answers to questions they care about;

Are we on track, or is there a hole in the plan? Is there an opportunity to get more value or reduce risk?

👉 If you’d like to discuss how effective prioritization could support your portfolio, book your Free Portfolio Briefing.

#Project Prioritization: Worked Example

Now let’s put this all together, with a 5-project portfolio for Demo Co.

This simplified example shows how to move from strategy → scoring → constraints → portfolio decisions using a data-led, structured approach.

#1. Build AHP Model – making strategy quantifiable

Criteria model agreed with leadership, then weighted at a Pairwise workshop to generate the following framework:

Now we know what matters to leadership and will use this framework to build our portfolio.

Measurement is also set up, with a mix of surveys and normalized data feeds. For the survey-based criteria we’ll use a 5-level, 0-100 scale, perfect for this use case.

For the data feeds we have business cases with financial projections.

#2. Score Projects - measuring alignment to strategy

We use business case data to measure Efficiency and Revenue, and set up assessment panels for Risk, Strategic Alignment and People, where groups of SMEs rate the 5 different projects, scoring each project using the sub-criteria scales.

This process builds buy-in, and also means we get strong data points as the foundation of our prioritization, which can be seen as a Total Value Score with criteria level breakdown:

It also creates a rich dataset of detailed insight at project level, which can be used to build a Project Scorecard, a great way to communicate the output from the process.

For example if we want to see why Process Automation was the strongest project:

Put this together and it means we have a ranking that people trust.

Next, we apply constraints.

#3. Apply Constraints – working out what we can afford

Our project forecasts are critical as we review which projects are the best-value-for- money, and which combination is achievable given resource limitations.

Let’s start with project forecasts for resource and budget:

Then apply constraints that leadership have put in place for the portfolio.

We do not have enough funding or people, so we need to prioritize. Approving all the business cases would be a disaster for delivery and break the budget, even if they have a good ROI and a sponsor with a loud voice.

#4. Prioritization Review – making decisions that support strategy

Show these results on the Prioritization Matrix (more on this later) and re-rank using value-for-money:

We can see that the Top 3 are the best projects – next let’s explore that selection vs. our constraints:

We can now make four clear project prioritization recommendations to leadership:

• Process Automation + CRM = Constraints OK → prioritize
• New Product + Cybersecurity = Constraints FAIL→ reject

This leaves Data Platform as our tricky “maybe” project where yes-no is too simplistic, as we’re just $0.5 and 2 IT FTE short.

Let’s explore options:

• Do not start immediately. It will slow down the two priority projects.
• Review plans to see if $0.5m cost saving is plausible across portfolio.
• Support IT bottleneck to look for ways to streamline their workload. For example, we have 1 PM “spare” – can a tweak of processes shift work over?
• Once Process Automation and CRM get started their exact requirements will be better defined - maybe they'll release capacity.

Final recommendation: → Not Yet.

 Work on potential efficiencies then revisit next quarter.

👉 Want to do this with your portfolio? Book a Free Portfolio Briefing.

#Visualisation: Project Prioritization Matrix and Beyond

Good visualization is fantastic for decision making. It is critical that you do not overload your leadership with data, as it will slow down the decision you need.

Aim for accessible charts updated regularly and trusted as reliable.

Here are our four favourites: simple, compelling and proven:

#Prioritization Matrix

• Compare Value to Cost to create a 2x2 view.
• Help stakeholders see trade-offs clearly.

#The Efficient Frontier

• Rank projects by Value for Money with cumulative data for Value and Cost (NB this is the same underlying data set as the Prioritization Matrix).
• Best value project on the left, then the next and so on.
• Draw a line where you have funds. If your project fits, it’s “in” – if not it’s “out”.
• Note that if you also apply resource constraints your selection may not be purely value-for-money based with bottlenecks also influencing inclusion.

#Resource Heatmaps

Resource is critical, so providing a simple visual indication of capacity vs. plan is an important way to communicate feasibility and risk.

We like a simple RAG view:

• Utilisation over 80% → Amber – brittle if anything goes wrong.
• Utilisation over 100% → Red – relying on out-performance or over-work.

💡Pro Tip: Create a Base Case Scenario with all the projects and then show this data to leadership can see the importance of prioritization.

#Project Roadmap

This is a fantastic way to show how prioritization plays out over time, adding a visual element to a list of start dates.

Making this a go-to feature of your monthly reporting is a great way to show what’s new, what’s changed and what’s shipped.

💡Pro Tip: Include key dates in project set-up so you know what can wait, and what is truly urgent.

Leadership see hundreds of data points every day. Making it easy for them to make good decisions will build the impact and profile of the PMO.

Analysis paralysis is a real risk, and good visualization is part of the mitigation.

👉 Prioritization - The Efficient Frontier

#Project Prioritization: Best Practices

Building a good prioritization model is a great start, but the real value kicker comes from how you use that model to drive what follows.

Don’t be fooled by complex consultancy speak or maturity model distractions: these are simple best-practice pointers that we’ve seen work for organizations of all sizes and sectors.

However, it is worth noting that this is where the line between Project Prioritization and Portfolio Management gets blurry, so think of it as everything you need to realise the potential value inherent in building an AHP model.

Leave the labels down to the folks promoting certifications.

👉 Want to go deeper on Portfolio Management? Steve Jenner wrote THE book (imaginatively named, “Managing Portfolios”)

#Build a Demand Management Funnel

A strong selection funnel that narrows down "too many projects" into a right-sized portfolio is critical in turning a prioritization model into a valuable PMO capability.

This process can be super-complex, but at a high level start with three goals: 

• Getting everything in one place is a big step forward if your start point is project chaos.
  
  This is especially true if you have “shadow portfolios” of untracked projects quietly consuming resources away from the scrutiny of the PMO. It is key that stakeholders are not left with an "easier" route to getting work done, if a prioritization process is going to work.

• Decide what assurance checks you always need to credibly assess project viability.
  
  Prioritization is central, but so too is the risk review, assurance checks, and technical signoffs. The point isn’t to build a ceremonial binder; it’s about enforcing a minimum standard of planning to reassure stakeholders (aka the people paying for the project) that their investment is viable.

• Establish authority to reject, or risk building a toothless process.
  
  If everything passes, then something is wrong. Be prepared to reject poor quality plans, unsponsored “ideas”, say “no” to projects that score poorly or "not yet" where bottlenecks preclude it.

👉 Demand Management Stage Gates: Build a Decision Funnel

#Build for Balance to Maximize Value

Effective portfolio selection needs to look at the distribution of value, and not just the raw total value score. Here's why:

• Benefits Sense Check: If five projects all promise 10% sales growth, is 50% growth actually realistic?
  
  Prioritization should challenge whether the combined portfolio outcome is credible, not just whether each individual business case looks right on its own.

• Optimise for Strategic Fit: Criteria weights are leadership's statement of intent.
  
  A balanced portfolio should reflect those priorities, rather than over-investing in one objective at the expense of others.

• Avoid Change Overload: Projects are enablers that hand new capabilities back to operations - this is when the benefits happen.
  
  Concentrating too much change in one area can overwhelm that team and reduce the likelihood that benefits are realised. Spread deliverables between departments and over time to reduce realization risk.

Optimize for value, fine tune for balance, and always aim to offer leadership choice to make judgement calls.

💡Pro Tip: In TransparentChoice you can use Strategic Fit as a scenario metric to show the link between criteria weight and value expected. It’s quite conceptual but super-powerful.

#Don’t let Prioritization become a free pass

There’s a tendency for prioritization to be seen as a one-off challenge rather an ongoing measurement of value potential.

This is dangerous for three reasons:

• Projects stray off value: Markets shift, stakeholders change, scope drifts.
  
  Regular stage gate reviews help address this by asking if the project remains worthwhile before releasing the next tranche of funding.

• Sunk costs are a fallacy: It doesn’t matter what’s been spent. It’s just about what’s left to go, and what the benefits are at the end.
  
  If this makes stopping the right move, then your process needs to enable this.

• Agility matters: There needs to be a constant tension between what’s new and what’s ongoing.
  
  “Stop” should be as well-received as “Go” at your Portfolio Board, or you run the risk of Zombie Projects diluting ROI by blocking higher value opportunities.

This is where regular iteration of the plan and single-minded focus on the projected outcomes of a portfolio are key. Nobody likes to stop a project: but most would agree it’s preferable to missing your goals.

Make it clear that this is the real choice.

👉 Read more about the Sunk Cost Fallacy, and other forms of Behavioural Biases which effect Project Management with Dr Bent Flyvbjerg

#Build Forecasting Capability

Prioritization needs capacity. That means every project request needs an estimate of how much resource it will consume before it can be meaningfully prioritised.

This information rarely exists upfront, especially during early triage. Project teams need to develop the confidence to look forward, and this is a great opportunity for the PMO to help.

• Look for benchmarks: Projects are usually less unique than you think.
  
  Dr. Bent Flyvbjerg's research on Reference Class Forecasting argues that organisations consistently improve forecasts by comparing work against similar projects completed in the past. Put simply, if you've done something similar before, start there.

• Be willing to be wrong: No forecast is ever perfect.
  
  Creating psychological safety around forecasting helps teams provide their best view rather than avoiding the conversation altogether. If a PMO's data is only looking backwards, their ability to influence outcomes drops, so it’s critical to work with delivery teams on making ‘best feel’ credible.
  
  
• Create an honest dialogue: Hidden buffers create hidden costs.
  
  Be deliberate about where contingency sits, how it is reported, and whether it is genuinely required. Be aware that exaggerating effort is the normal response when people are consistently over-utilised. Trust needs to work both ways.
  
  
• Encourage choice: Scenarios are a powerful way to expose trade-offs.
  
  A "Short Fat" plan with more resource may accelerate value, while a "Long Thin" plan may reduce delivery pressure around bottlenecks but push back benefits.

Forecasting capability develops over time. Be patient, coach teams through the process, and focus on continuous improvement rather than perfect accuracy.

👉 Read more about Reference Class Forecasting from Dr. Bent Flyvbjerg: From Nobel Prize to Project Management: Getting Risks Right

#Connect Prioritization, Benefits, Capabilities and Deliverables

These are not independent processes, but a series of connected steps that collectively represent the route by which a PMO can drive value:

• Prioritization identifies value - why projects are worth doing using a portfolio-wide framework that lets us compare projects to one another. 
  
  Make it clear that there is accountability for these projections, so that the system is not gamed, with inflated claims used to fake prioritization.
  
  
• Deliverables create Capabilities - the outputs that make benefits possible.
  
  These are generally the focus through the delivery cycle, but a value-led approach ensures that teams are made aware of the link between Deliverables and Value so as they make trade-offs they know what really matters to stakeholders.
  
  
• Benefits define the intended Outcomes - the specific measurable improvements each project is expected to deliver.
  
  These represent the goals of the team tasked with taking new Capabilities and putting them to work. They should be supported with measurement, even if this means adding a pilot phase to deployment.
  
  
• Benefits Realization measures actual Outcomes - and also helps improve the whole system through learning where it fails most often.
  
  Do we over-inflate our forecasts?
  Does scope creep undermine value?
  Do we fail to realize value when we operationalize projects? 

This is the Golden Thread of value. It starts with prioritization and ends with benefits realization, and keeps value central to delivery. 

👉 Benefits Management: Ultimate Guide to Frameworks & Processes

#Make it easier to follow the process (than to resist)

The single biggest factor in getting prioritization to work is to have buy-in to the process.

If compliance is seen as a red-tape heavy route to resource, while corridor conversations offer the same outcome for a fraction of the effort then your processes will be bypassed and your PMO sidelined.

• Don’t leave a back-door approval route. Once it’s known that templates are optional, they are useless. Close-down those “shadow portfolios” that consume resource without accountability.
  
  
• Look for ways to make things easier. Before adding a new ask, take something out. If your process means people are missing their kid’s sports, you will lose the goodwill that any new way of working needs to bed-in.
  
  
• Give Execs simple clear choices. Scenario A or B. Not reams of scoring data. They don’t want to see all the workings out, just a well-presented set of choices that gives them control.
  
  
• Work with Finance to connect to their planning processes. Both of you represent a check on spending, so don’t sit in separate silos competing, adding work for others and creating ambiguity on outcomes.
  
  

If doing the right thing is also the path of least resistance, then it will work far better than an overly complex ‘mature’ model.

💡Pro Tip: Always challenge your process to be as simple, fast and effective as possible with just enough governance.

#Project Prioritization: 7 Common Mistakes to avoid

Most prioritization failures are avoidable. Unfortunately, they are also popular. If you’ve made a couple don’t despair. You’re not alone, and the key point is to learn and improve.

Ideally before your PMO gets closed.

#1. Treating Strategic Alignment as a tick-box

If everything aligns to strategy, nothing does.

Strategic alignment must be translated into criteria, weighted properly, and scored objectively. Self-certification of a pet project does not count.

#2. Ignoring Risk before Selection

Risk is not something to discover after approval.

It’s a factor in the selection model, like a discount on the value linked to the project’s outcomes. Modelling can be simple, or detailed, but it’s important to remember that leadership hate surprises, so don’t offer massive ROI at prioritization, only to come back with off-the chart risk a week later.

#3. Pretending Capacity and Bottlenecks don’t matter

A portfolio that cannot be resourced is not a plan. It’s a delivery-risk trap for the PMO.

If you have a team utilized at over 80% for a sustained period, your portfolio will suffer. Murphy’s Law means something always goes wrong. Balls dropped, sea of Reds appear on trackers, dependencies popping up.

This is avoidable with up-front Capacity Planning. Identify bottlenecks during prioritization, then stagger start dates to reduce the pressure on your most on-demand resources.

👉 See how TransparentChoice tackles Capacity Planning

#4. Making Data Collection painful

The data required for prioritization does not normally exist. People need to spend time working on forecasts or scoring projects against sub-criteria.

This is a good thing: better planning → better outcomes.

However, it’s more work, so should always be accompanied by efforts to support users. That means a PMO should always be pruning:

• Do you do anything with that data field? If no, cut.
• Do we decide anything at that meeting? If no, make it an email update.
• Is there any double-keying data? If yes, connect at source. Let the tech help.

👉 See how TransparentChoice tackles Data Collection for Demand Management

#5. Disconnecting Decision Authority from Process

If demand management can be overridden, or stage gates always passed, then authority and process are not joined.

That is not governance. That is admin. It means you get the extra task linked to prioritization, while missing out on the benefits of driving better outcomes.

This is often the case when a PMO gets closed. It’s simply not been given the licence to succeed, only a mandate to report on failure.

💡Pro Tip: For a PMO to implement prioritization effectively they need to integrate AHP with effective governance and high-impact change management. Good job we have a hand guide that explains exactly how available here

#6. Treating Mandatory as “Selected”

Some mandatory projects are exactly that: Must Do commitments that need to jump the line.

However, many are less black and white.

There is often scope to build a portfolio where projects are evaluated vs. the question: “what happens if I ignore this project”, rather than using the AHP model that focuses on value.

The goal here is to reduce residual portfolio risk by offering alternative scenarios:

• Can I nudge the projects back to open capacity?
• Can I get a “Plan B” which strips the project down the absolute regulator basics?
• Can I offer leaders choice: tolerate extra risk in exchange for greater investment in growth?

It’s also important to protect “Mandatory” as a sneaky backdoor for Pet Projects, with extra features added to core requirements on the basis that formal prioritization would (rightly) say no.

💡Pro Tip: Build a second AHP model, focused on scoring mandatory projects. Same principles, different outcome.

#7. Using Excel at scale

Excel is fine to start.

It is familiar, flexible, and cheap; but in the same way a “free puppy” is cheap.

But at scale, spreadsheets struggle:

• No collaboration for weights and scoring.
• Struggles when multiple different people updating projects in parallel.
• Submission discipline relies on trust, with no access controls.
• No formal version control, leaving you trying to figure out if “Version 3.21 Final _UseThis_V2” was used at the last governance update.
• Scenario modelling is manual: no AI-automation, cloning or switching.
• Every chart or work-around takes time for the PMO to build.
• Excel is brittle. Adding new projects, resource groups or reporting metrics becomes a significant task, taking time and increasing the potential for hidden bugs.

The problem is not Excel. The problem is pretending Excel is an enterprise decision system for prioritization, and that the PMO’s time to make good the difference is “free”.

👉 Read more on why free spreadsheets could be costing you millions

#Project Prioritization: Case Studies

Good prioritization is not theory.

It changes what gets funded, what gets stopped, and how confidently leaders make portfolio decisions.

The examples below show how structured prioritization can help organizations move from opinion-led debate to clearer, more defensible choices.

#Harbor Foods — From Backlog Chaos to Executive Buy-In

"It really used to be the loudest voice, the squeaky wheel… or the IT people would just grab the project because it was cool to work on that one... We never really looked at what is most valuable for the business, what aligns with the strategic goals of the business this year."

Anette Smith, PMO Director Harbor Foods

• Challenge: Harbor Foods faced a large backlog of project requests, with 134 projects in the queue and some requests dating back years. Without a structured prioritization process, decisions were often shaped by the loudest voice, IT preferences, or whichever request seemed most urgent at the time.
  
  
• Approach: The PMO introduced a transparent, business-driven prioritization process using TransparentChoice.
  
  Business leaders set the weights, stakeholders answered the evaluation questions, and projects were assessed against the priorities the business had agreed mattered most for that year.

• Outcome: The process helped move decision-making away from politics and guesswork toward business-value-led choices.
  
  Leaders gained clearer visibility across the portfolio, the PMO strengthened its credibility, and executive buy-in improved because projects could be linked more directly to business goals.

• Why it matters: Harbor Foods shows that prioritization is not just an analytical exercise. For a developing PMO, it can also be a trust-building mechanism: a way to show leadership what exists, what matters, and what should happen next.

👉 Learn how Harbor Foods built executive buy-in through prioritization

#APA — Making Strategic Planning Actionable

"What we have today is a real intense feeling of satisfaction and confidence that when we say we’re gonna do something, we have the ability to see it through and do it."

Mike Welch, Strategy Realization Office (SRO) Lead at the American Planning Association (APA)

• Challenge: APA’s challenge was not simply choosing between projects. It needed to translate long-term strategic objectives into a practical decision framework that could guide real portfolio choices.
  
  And this was not a mature PMO, but a new team.

• Approach: APA used structured prioritization to break strategic goals into criteria and evaluate initiatives against them.
  
  This helped shift the conversation from opinion and advocacy toward structured judgement: which initiatives best supported the agenda agreed with the Board, and which should not consume capacity.

• Outcome: The process helped APA focus on the work most closely aligned with its strategic priorities.
  
  They replaced subjective decision-making with TransparentChoice prioritization, removed redundant programs, strengthened alignment between Board priorities and execution, and reported a doubling of strategic ROI.

• Why it matters: APA is a strong example of prioritization as a strategy-execution discipline.
  
  The point was not to add PMO bureaucracy; it was to make strategic intent scoreable, comparable, and actionable from the outset.

👉 Read about APA and how it took control of its portfolio with prioritization

#Energinet — Making Waste Visible Enough to Stop

"When 60 projects have top priority, you can say there is no priority…. and around one third of projects were obsolete before they were even finished."

Director of Strategic IT

• Challenge: Energinet, Denmark’s electricity and gas operator, faced a familiar portfolio problem at significant scale: too many projects treated as high priority, including work that no longer aligned with corporate priorities, had become obsolete, or was consuming resources that could be better used elsewhere.
  
  
• Approach: Energinet translated strategic goals into weighted criteria, scored projects consistently, and used transparent value-for-money comparisons to support portfolio decisions.
  
  This created a clearer basis for discussing which projects still deserved investment and which no longer did.

• Outcome: The process helped identify and eliminate low-value IT projects, freeing resources and contributing to more than €6 million in savings.
  
  Just as importantly, executives and project managers gained a shared view of what mattered and why.

• Why it matters: Energinet shows one of the most commercially powerful roles of prioritization: making hidden waste visible.
  
  When leaders can see value, cost, and alignment clearly, stopping work becomes a rational portfolio decision rather than a political argument.

👉 Learn how Energinet saved over €6 million through project prioritization

#Life Sciences — Scaling Planning Beyond Spreadsheets

"Moving away from spreadsheets was a huge win for us. The process was far more efficient, easier to manage, and gave leadership much better visibility into planning decisions."

Finance Director

• Challenge: Life sciences portfolios are complex. They often involve R&D uncertainty, regulatory pressure, commercial trade-offs, specialist expertise, capacity bottlenecks, and high opportunity cost.
  
  In that environment, planning needs to support growth while also managing risk and constraints.

• Approach: The client used structured prioritization as part of its annual planning process, initially with spreadsheet and consultancy support and later through a software-based approach.
  
  This helped create a more disciplined planning process as the portfolio grew in scale and complexity.

• Outcome: The company replaced spreadsheets with a unified TransparentChoice platform for annual planning, reduced annual planning time, improved collaboration across regions, and built an enterprise-wide, risk-adjusted portfolio view.
  
  That means they kept the data-driven prioritization they had built over a decade but took out the time-consuming bottleneck of a hard-to-manage spreadsheet.

• Why it matters: This client shows why spreadsheet-based prioritization can work – but the “free” tool takes a lot of effort and can become a constraint as portfolio complexity increases.
  
  When planning involves multiple regions, risks, scenarios, and capacity trade-offs, the value is not just better scoring — it is faster, more collaborative portfolio decision-making.

👉 Learn how a global life sciences company scaled annual planning and prioritization

#Project Prioritization: Free Templates and Downloads

We’ve covered a lot here, but if you’re ready to go further on the journey to a high value portfolio then you’ll want more.

The simplest next step would be to reach out and arrange a free 30-minute Portfolio Consultation.

You can also benefit from Free downloadable materials where we share our best practice:

• Downloadable E-Book Ultimate Guide
• Project Criteria E-Book: 80 Example Criteria
• 10-Step Guide to Prioritization Implementation for PMOs
• Downloadable Benefits Management E-Book
• Downloadable Excel Template

👉 See how to deliver Project Prioritization for yourself on our Software Page.

#Project Prioritization: The Case for Change

If you need to make the case for better prioritization land with leadership, we recommend that you focus on outcomes — not process.

Effective prioritization is not a PMO maturity upgrade.
It is a way to deliver more value with the same resources.

These four arguments consistently land with senior stakeholders:

1. Stop Wasting Money

Every low-value project consumes budget, capacity, and attention.

Prioritization reduces:

• Failed or low-impact projects
• Rework and sunk-cost continuation
• Investment in initiatives that never deliver meaningful outcomes

Even a small improvement in project selection can unlock significant ROI upside.

2. Deliver High-Value Work Faster

When too many projects run in parallel, everything slows down.

Prioritization improves:

• Time-to-value
• Focus on strategic initiatives
• Speed of delivery for high-impact work

Fewer projects in progress means faster results, bringing benefits forward.

3. Use Resources More Efficiently

Most organizations are constrained by people as much as budget. Prioritization helps:

• Avoid overloading bottleneck teams
• Reduce context switching and inefficiency
• Align scarce expertise to the highest-value work

That makes it the best way to increase throughput without increasing headcount.

4. Build a Decision-Making Capability

Without structure, prioritization becomes political, changeable and hard to track. With the right approach, prioritization becomes a:

• Stable decision-making that makes governance more effective
• Pillar for driving culture of accountability
• Platform for better collaboration that cuts silo-based waste

This is especially important for PMOs who waste a lot of time due to poor decision-making in the governance process.

The Bottom Line: Prioritization improves outcomes. It ensures that:

• The right projects get funded, with fewer low-value fillers.
• High-value work gets delivered faster, bringing benefits forward.
• Teams collaborate more effectively, improving productivity and morale.
• Decision-making develops as an organizational capability.

Apply these outcomes to your portfolio to show that prioritization is an investment not a cost.

Set KPIs for financial justification, then overlay examples where current ways of working have meant poor outcomes, to shape a compelling emotional story alongside.

You need to work out which elements land best with your leadership, so you can demonstrate the upside to fixing prioritization in terms they find relatable. Some will want ROI; others may respond to the opportunity to improve collaboration.

The good news is that prioritization done well delivers both at a scale that will more than justify the investment.

👉 Need help building your Case for Change? Book a free consultation.

#Measuring the Value of Prioritization: Tracking Performance

Be prepared to show the positive impact of prioritization, with measurable metrics that you build into your deployment.

We recommend:

This turns prioritization from a one-off governance exercise into a measurable PMO value engine, and in doing so will help cement your PMO’s status as a key asset for your organization.

Tracking value is the key end-point to a practical prioritization delivery. Start with scope, end with results, use the best practice in this guide for everything in-between.

👉 Ready to do this yourself? Download the PMO's 10-step guide to implementing prioritization

#Project Prioritization Software

Let’s focus now on bringing the Decision Science to life.

Understanding the math behind AHP and portfolio constraints is one thing; running pairwise comparisons across dozens of stakeholders with multiple projects in a spreadsheet is another.

Without the right system, manual data collection quickly becomes a bottleneck, while modelling and visualization are limited by Excel inflexibility.

With it, you get a better model for less manual effort, giving you time to focus on building buy-in and nurturing decision capability.

Here’s why:

• AHP ready: Integrated algorithms that define AHP are built in, with consistency ratios, normalized data sets, matrix math, pairwise surveys and ‘small crowd’ disagreement analysis baked into a user-friendly interface.
  
  Add an editable criteria library, and you can have a model live in minutes.
  
  
• Data collection at-scale: Adding data needs to be easy.
  
  Whether that’s user-generated requests, delegated ownership to stakeholders, integration with other tools, or a custom import via a spreadsheet, the software’s job is to help the PMO collect quality data with as little effort as possible.

• Bottleneck warnings: Aggregate plans to see which teams are in danger of becoming your bottleneck, then build a solution to mitigate the risk, through adding capacity, cutting projects or delaying start dates.
  
  The software makes identifying the problem easy, so the PMO can focus on finding the solution.
  
  
• Data visualization: Produce and refresh the key artefacts leadership need to make decisions.
  
  From live roadmaps and prioritization matrices to resource heatmaps and efficient frontiers, the data is always presentation-ready.
  
  
• Rapid What-If scenarios: The PMO’s role is to offer choice, and that’s exactly what you get from having integrated constraints built into an algorithmic selection tool.
  
  Pin specific projects in or out, flex weights, change project plans or change constraints to generate and compare alternative portfolios in seconds.

• Risk-adjustable financial modelling: Customize your financial datasets, with as much or as little detail as you need.
  
  Next, overlay reportable metrics and a live risk adjustment factor to ensure that your business benefits can drive your model, feed your business case and track progress from one place.

• Baseline Reporting: Lock in your prioritization and then track vs. plan, to give leadership a monthly view of progress without scrambling for data ahead of governance.

And it’s less work than you think.

This is not a slow roll-out PPM solution. Cloud-based deployment can be live in minutes, and a planning cycle executed in weeks.

The biggest time commitment is getting leadership to agree and weight criteria, but this is not software onboarding. It’s building the alignment and buy-in that is critical to successful prioritization.

Here’s what you’ll need in our data prep template.

• Criteria
• Projects
• Project Benefits
• Resource and Cost Estimates
• Stakeholders

👉 See how to deliver Project Prioritization for yourself on our Software Page.

#Make Prioritization your Priority

By this point, the case should be clear: prioritization is good for ROI, good for colleagues, and good for the PMO.

The problem is rarely disagreement. It is distraction. Fires to extinguish. Updates to publish. Projects already in flight. Longer-term fixes get pushed aside. And yes, leadership time is not easy to get into the diary.

That is why the final ingredient is resolve: the commitment to make prioritization a priority, and the resilience to stick with it.

👉 Need help to get focused back on solving prioritization? Book a free consultation.

#Frequently Asked Questions About Project Prioritization

#What is project prioritization?

Project prioritization is the decision-making capability used to decide which projects to start, stop, delay, or accelerate based on value, constraints, and buy-in.

#How do you prioritize projects?

Build a complete project list, define value through criteria, weight those criteria, score projects consistently, apply cost and capacity constraints, then select and sequence the best deliverable portfolio.

#Who should be involved in project prioritization?

Leadership owns the trade-off, but the PMO usually owns the process. Finance, Strategy, delivery teams and subject-matter experts all need to contribute because prioritization depends on strategy, investment logic, capacity and delivery reality.

#What are the best project prioritization criteria?

Common criteria include strategic alignment, financial value, efficiency, risk mitigation, stakeholder impact, and delivery risk. Other useful criteria include urgency, feasibility, dependencies, compliance, and benefit confidence.

#What is the best project prioritization method?

For simple backlogs, methods like MoSCoW, RICE, WSJF, or Eisenhower can help. For complex project portfolios, AHP is usually the strongest approach because it supports multi-criteria weighting, stakeholder input, consistency, and buy-in.

#What is a project prioritization matrix?

A project prioritization matrix is a visual tool that compares projects, often using value vs cost or value vs effort. It helps communicate trade-offs but requires a robust definition of “value” that comes from a proper prioritization model.

#What is the difference between project prioritization and project selection?

Project prioritization evaluates and ranks projects based on value and criteria. Project selection uses those scores plus constraints — budget, capacity, risk, dependencies — to choose which projects actually move forward.

# How can I turn this best practice into a practical program of work in my organization?

We have built a simple guide that takes everything we've covered here and turns it into a practical 10-step approach that any PMO can follow. Download it now if you're ready to start prioritizing the right way.

👉 Grab the free guide here for your simple 10-step solution for fixing prioritization

#How often should projects be reprioritized?

Projects should be reviewed whenever strategy, capacity, risk, benefits, or assumptions change. Quarterly portfolio review is a practical starting point for many organizations, with lighter updates as part of monthly governance. Monthly is ideal once processes are light enough to enable frequent updates. 

#Who owns project prioritization?

The PMO often facilitates the process, but Strategy, Finance, executives, and portfolio governance all need to be involved. The key is collaboration between the teams that define direction, control investment, and understand delivery reality.

#Can you prioritize projects in Excel?

Yes, especially at small scale. But Excel becomes risky when collaboration, auditability, version control, scoring consistency, scenario planning, and governance matter. The question is not so much “can you” as “would you really want to”?

#How can AI support project prioritization?

AI can help prepare data, identify duplicates or missing information, support scenario generation, and explore portfolio options against budget and resource constraints. When it comes to selection, AI thrives on a well-structured data set, so capturing value in a consistent framework will greatly enable endeavours to use technology in decision making.

#How does AHP help with project prioritization?

AHP helps organizations compare criteria, derive better weights, reduce bias, involve stakeholders, and create defensible project scores. It turns prioritization from opinion into structured decision-making. In short, AHP is weighted scoring with stronger decision science behind it.

#Do I need consultancy support to implement TransparentChoice?

Short answer, no. It’s a simple solution and comes with a support package to customize set up to your portfolio. However, we have an excellent partner network in case you need help with the organizational change that helps you get the most from having better data.

#What is the difference between AHP and RICE prioritization?

RICE (Reach, Impact, Confidence, Effort) is a feature-level scoring formula primarily used by software product teams. AHP (Analytic Hierarchy Process) is a multi-criteria decision-making framework designed for enterprise project portfolios. AHP uses pairwise comparisons to reduce scoring bias and build executive consensus across complex, competing strategic goals.

#How do you prioritize projects when resources are constrained?

Prioritizing under resource constraints requires moving beyond simple ranked lists. PMOs must pair prioritization scores with capacity optimization. By evaluating project value against available headcount, budget, and specialized skill sets, portfolio optimization tools reveal the combination of initiatives that help identify the portfolio that maximizes strategic value while avoiding obvious over-allocation.

#Final Thought: Prioritization Is Where Strategy Gets Real

Project prioritization is not about scoring projects.

It is about building a decision-making capability that turns strategy into action.

It is where leaders decide what value means. It is where PMOs protect delivery teams from overload by connecting capacity to approval. It is where weak projects get challenged before they consume money, people, and goodwill. It is where benefits management starts, because you cannot realize value from projects you should never have selected.

Do this well and your PMO becomes a value engine.

Do it badly and the organization keeps pretending that more activity means more value.

It doesn’t.

More value comes from better decision-making, built around the three key prioritization components:

Value + Constraints + Buy-In.