To handle competing project priorities, organisations need a transparent, criteria-based process. This means defining clear prioritisation criteria (strategic fit, ROI, risk, urgency), scoring each project against them, making trade-offs visible to stakeholders, and holding a regular portfolio review cadence so priorities can be adjusted as business conditions change.
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.
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.
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:
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.
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.
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.
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.
Conflicting priorities are best resolved by reference to an agreed prioritisation framework rather than by seniority or negotiation. Score each competing project against defined criteria, make the scores visible, and escalate only where the criteria genuinely do not resolve the conflict. The portfolio review forum is the right place for escalated priority decisions.
The most common and effective criteria are: strategic alignment (how directly does the project support a defined objective), financial return (ROI or NPV), risk exposure (the cost of not doing it), urgency (deadlines, regulatory requirements), and resource efficiency (return per unit of investment). Weight the criteria to reflect the organisation’s current strategic priorities.
Most organisations benefit from a monthly portfolio review that includes a prioritisation check, supplemented by an ad hoc review process for significant changes, such as a major new request, a project cancellation, or a shift in strategic direction. Quarterly reviews alone are too infrequent for organisations operating in fast-changing environments.
Communicate in writing to all affected project sponsors, including the decision, the rationale, the impact on their project, and the timeline for any changes. Acknowledge the inconvenience where a project has been deferred or descoped. Follow up verbal conversations with written confirmation. Transparency in the reasoning reduces the volume of subsequent challenges.
Keto AI+ is a strategic operating system that goes beyond what project management tools can do. Click below to find out more.
Most portfolio teams now use AI somewhere in their work. In a 2026 survey of 300 PMO and portfolio leaders, 91% said their organisation is piloting or actively using AI in project delivery. Look at where that AI is used, though, and the picture changes. Reporting and dashboards come first. Only 26% use AI to prioritise or reprioritise work, and only 20% use it for scenario planning.
