When managing multiple projects, one of the toughest decisions isn't what to deliver.

It's deciding what deserves attention first.

In many organisations, project priorities are influenced by budgets, deadlines, stakeholder expectations, and operational demands.

But the largest investment isn't necessarily the most urgent. And the loudest stakeholder doesn't necessarily represent the greatest business risk.

Effective project prioritisation requires understanding not only the value a project creates, but also the consequences of not undertaking it.

Imagine an organisation with three projects competing for limited capital funding and resources.

Project A — $2 million: Operational Efficiency

An equipment upgrade designed to improve productivity, reduce operating costs, and deliver long-term financial benefits.

Project B — $150,000: Equipment Replacement

A critical piece of ageing equipment with increasing maintenance requirements and a growing likelihood of failure. An unexpected breakdown could significantly disrupt production.

Project C — $500,000: Safety and Compliance

An engineering upgrade required to address a significant safety risk and meet compliance obligations.

Which project should come first?

Project A offers significant business value.

Project B protects operational continuity.

Project C addresses safety and compliance exposure.

The answer isn't necessarily determined by investment size or expected financial return.

It depends on the risks, consequences, timing, and obligations associated with each project.

A risk-based approach helps organisations move beyond subjective decisions.

1. Safety and Compliance

What are the consequences of delaying the project? Are existing controls adequate? Are there mandatory compliance requirements or unacceptable risks?

2. Operational Continuity

Could postponement result in equipment failure, unplanned downtime, or production losses?

3. Risk Exposure

What is the likelihood and impact of the risk materialising? Will exposure increase if the project is delayed?

4. Strategic Value

How does the investment contribute to organisational objectives, operational efficiency, or long-term business performance?

5. Time Sensitivity

Will delaying the project increase costs, create additional risks, or result in missed implementation opportunities?

These factors should be considered alongside resource availability, dependencies, and delivery feasibility.

Importantly, an intolerable safety risk or mandatory compliance obligation should not be overridden simply because another project offers greater financial benefits.

This is an important distinction in project portfolio management.

Project risk refers to uncertainty that could affect delivery, such as cost overruns, schedule delays, design changes, or contractor performance.

The risk of not undertaking a project refers to the consequences of leaving a business problem unresolved.

Consider Project B.

Replacing the equipment introduces delivery risks, including installation delays and commissioning challenges.

However, postponing the replacement may expose the organisation to an increasing likelihood of equipment failure and costly production interruptions.

Both sides of the decision matter.

Sometimes, accepting a manageable project delivery risk is preferable to continuing to carry a significant operational risk.

Project priorities should evolve as business conditions change.

An equipment replacement considered medium priority six months ago may become critical following repeated failures.

A project previously classified as urgent may become less critical after effective interim controls are introduced.

This is why project portfolios require regular review.

Risk assessments, business cases, and project priorities should reflect current conditions rather than assumptions made during the annual budgeting process.

Good governance isn't about keeping the original priority list unchanged. It's about making informed decisions as circumstances evolve.

Project prioritisation is more than deciding which projects receive funding first.

It's about balancing risk reduction, business value, strategic alignment, and available resources.

A $150,000 investment may be more critical than a $2 million upgrade if it prevents a major operational disruption.

Similarly, a safety-related project may require immediate action regardless of its financial return.

The goal isn't simply to prioritise the highest-risk project. It's to prioritise investments based on the risks they address, the value they create, and the consequences of delaying them.

Effective portfolio management isn't about keeping every project moving.

It's about ensuring the organisation is investing its limited resources in what matters most.

When resources are limited, how does your organisation decide which projects come first?

Are priorities driven by risk exposure and business value, or by deadlines and stakeholder pressure?

I'd be interested to hear your perspective.

The Saturday Mindset — Weekly insights on project management and engineering.

If you haven’t already, subscribe here: https://vandersonbaril.com/newsletter/

Thanks for reading, and until next Saturday!