How to Prioritise Projects When You Don’t Have Enough Resources
Most organisations do not have a shortage of ideas.
Project prioritisation based on strategic value and limited resource capacity
They have a shortage of capacity.
That is where project prioritisation becomes real.
It is easy to say every project is important when there are enough people and enough money.
The difficult part starts when five projects all need the same two people.
At that point, prioritisation stops being a strategy exercise and becomes a resource decision.
Not every project can be first
One of the biggest mistakes organisations make is approving too many projects and then hoping the resource problem will somehow sort itself out later.
It usually does not.
You end up with:
people spread too thin;
projects moving slowly;
constant reshuffling;
frustrated project managers; and
senior leaders asking why everything is delayed.
It is a bit like opening ten taps when you only have enough water pressure for four.
Everything still runs.
Just badly.
Start with strategic value
The first question should be:
Why does this project matter?
A useful prioritisation process should consider things like:
strategic alignment;
expected business value;
regulatory or mandatory need;
financial return;
risk reduction;
customer impact; and
urgency.
This helps separate projects that are genuinely important from projects that are simply loud.
Then bring capacity into the decision
A project can be strategically attractive and still be impossible to deliver right now.
That matters.
Prioritisation without capacity is only half a decision.
If three high-priority projects all depend on the same specialist team, leadership needs to decide:
which one goes first;
which one waits;
whether additional capacity can be brought in; or
whether scope and timing need to change.
This is where portfolio management becomes practical.
Do not prioritise only once
Prioritisation should not be something that happens at the start of the year and then disappears.
The portfolio changes.
Strategy changes.
Costs change.
Resources leave.
New regulatory work appears.
Projects that made sense six months ago may no longer deserve the same level of investment today.
A healthy portfolio should be reviewed regularly.
Not because projects should be constantly cancelled, but because priorities should reflect current reality.
Separate “important” from “ready”
Another useful distinction is between a project that is important and one that is ready to execute.
A project may be strategically valuable but still lack:
a clear business case;
confirmed resources;
agreed scope;
sufficient funding; or
required dependencies.
That project may deserve a high priority, but it may not be ready to consume capacity yet.
This is why a prioritisation funnel is useful.
Projects should move through evaluation before they are selected for execution.
Resource allocation should follow priority
Once priorities are clear, resource allocation should support them.
That means scarce capacity should not automatically go to the project manager who asked first or shouted loudest.
It should go to the work the organisation has decided matters most.
A strong sequence is:
Strategy → Prioritisation → Capacity → Allocation → Delivery
That creates a clear link between what leadership says matters and where people are actually spending their time.
Be willing to say “not now”
One of the hardest portfolio decisions is not saying no.
It is saying:
Not now.
That can be the right decision.
A project delayed until the right resources are available may have a much better chance of success than one started immediately with half the team it needs.
Starting everything is not the same as progressing everything.
Sometimes the strongest portfolio decision is to stop creating queues of half-started work.
The key takeaway
Project prioritisation is not about ranking projects for the sake of producing a list.
It is about making trade-offs.
Which work matters most?
What capacity do we actually have?
Where should that capacity go?
And what should wait?
When those decisions are made clearly, resource allocation becomes easier, delivery becomes more realistic, and the portfolio becomes much easier to trust.
Put stronger prioritisation into practice
ProjectFiles connects strategic objectives, project prioritisation, resource capacity, allocation and delivery governance in one controlled environment.
Clarity. Control. Confidence.
Numbers that hold up when challenged.
