How to Handle Competing Project Priorities: A Practical Guide

Competing project priorities are not a sign of poor planning. They are an inevitable feature of any organisation that is running multiple initiatives in parallel. The question is not how to eliminate the competition, but how to resolve it consistently, transparently, and with the minimum amount of friction and delay.

Without a structured approach, priority conflicts tend to be resolved through seniority, persistence, or whoever happens to be in the room. This produces decisions that feel unfair to some stakeholders, are difficult to reverse when circumstances change, and leave the PMO in the uncomfortable position of adjudicating between business units without clear criteria to stand behind.

Why competing priorities are a portfolio problem, not just a project one

It is tempting to treat competing priorities as a project management problem: which project manager should get the shared resource? Which deadline takes precedence? But these questions only arise because of decisions made at portfolio level: too many projects approved relative to capacity, insufficient transparency about relative priority, and no clear criteria for resolving conflicts.

Fixing priority conflicts at project level is treating the symptom. The structural solution is a portfolio-level prioritisation framework that makes the relative value of every project clear to everyone, before conflicts arise.

Step 1: Establish shared prioritisation criteria

The most important single action an organisation can take to reduce priority conflicts is to agree, in advance, what criteria will be used to rank projects. When everyone knows that projects are ranked by strategic alignment, financial return, risk, and urgency, and when those criteria have been agreed at executive level, individual priority debates have a neutral reference point.

Common criteria for portfolio prioritisation include:

• Strategic alignment: how directly does this project support a defined organisational objective?
• Financial return: what is the expected ROI, NPV, or cost saving?
• Risk: what is the cost or consequence of not doing this project?
• Urgency: is there a regulatory deadline, contractual obligation, or market window?
• Dependencies: does this project enable or depend on other work in the portfolio?

Step 2: Score and rank projects transparently

Apply the agreed criteria to every project in the portfolio and produce a ranked list. Use a weighted scoring model so that criteria reflecting the organisation’s current strategic priorities carry more weight. Make the scores visible, not just the rankings, so that project sponsors can understand why their initiative sits where it does.

Transparency is critical here. A ranked list produced in a spreadsheet that only the PMO can see does not resolve priority disputes. A scored portfolio view accessible to all project sponsors reduces the volume of escalations because the reasoning is visible.

Step 3: Make trade-offs visible

When two projects are competing for the same resource, the portfolio view should make the trade-off explicit: if Resource A moves from Project 1 to Project 2, what is the impact on Project 1’s delivery? Which strategic objective does that put at risk?

Making trade-offs visible in this way shifts the conversation from ‘my project is more important’ to ‘here is what we lose and gain by making this decision’. It also elevates the conversation to the right level: trade-offs that affect strategic outcomes should be decided by people with strategic accountability, not resolved by project managers in bilateral conversations.

Step 4: Hold a regular portfolio review cadence

Prioritisation is not a one-off event. Priorities change as market conditions shift, projects are completed or cancelled, and new requests arrive. A regular portfolio review, typically monthly or quarterly depending on the pace of change, is the mechanism by which the organisation keeps its prioritisation current.

The review should include: a check on all active projects against current strategic priorities, an assessment of resource utilisation and upcoming capacity constraints, review of any new project requests, and formal decisions on any reprioritisation required.

Step 5: Communicate decisions clearly

A reprioritisation decision that is made but not communicated causes almost as much disruption as no decision at all. Project sponsors need to understand not just what has changed, but why, and what it means for their initiatives.

Good prioritisation communication includes: the decision, the criteria that led to it, the impact on affected projects, and the timeline for any changes. Written communication is preferable to verbal for anything that changes a project’s approved status, so there is a clear record.