A portfolio can contain many defensible projects and still be a poor portfolio.
Executives often encounter project prioritisation as a ranking exercise: score every proposal, place the highest numbers at the top, and fund until the budget is exhausted. The logic appears disciplined, but it can produce a portfolio that is overloaded, strategically narrow or dangerously dependent on the same capabilities.
The reason is simple. A portfolio is a system, not a queue.
Every initiative changes the conditions under which the others must succeed. Projects compete for specialists, operational downtime, procurement capacity, data, executive attention and organisational tolerance for change. Some initiatives create dependencies that improve the value of later investments. Others duplicate capability or concentrate risk. A portfolio decision must therefore consider combinations, not only individual merit.
The Strategic Context
The supplied project-selection material distinguishes operational spending from capital investment and describes project portfolios as mechanisms for managing strategic risks attached to accepting or rejecting work. It also presents a project portfolio matrix attributed to Gray and Larson (2014), classifying initiatives by technical feasibility and commercial potential into “bread-and-butter”, “pearl”, “oyster” and “white elephant” types.
The labels are less important than the underlying insight: different projects play different roles in the enterprise.
Some sustain the existing economic engine. Some extend proven capability into attractive opportunities. Some are difficult, uncertain bets with significant upside. Some have lost their original justification and should be exited.
A portfolio that maximises only near-term certainty can starve future growth. A portfolio dominated by high-uncertainty innovation can exhaust cash and management attention. A portfolio full of small improvement projects may feel busy while failing to address structural threats.
Balance is therefore strategic, not cosmetic.
What Leaders Commonly Misread
The first misread is the phrase “high priority”. If ten initiatives are all high priority, the organisation has not prioritised. It has labelled.
The second is to assume that a positive business case creates an entitlement to proceed. Investment appraisal asks whether an initiative may create value. Portfolio governance asks whether it should receive resources now, relative to alternatives and constraints.
The third is to manage capacity after selection. Teams are often asked to “work it out” once initiatives have been approved. This transfers an executive allocation failure into an operational scheduling problem.
The fourth is to treat stopped projects as failure. In reality, a portfolio that never stops anything may be failing to respond to evidence.
Reframing the Issue
The correct unit of optimisation is not the project. It is the enterprise portfolio under constraint.
That requires leaders to consider at least five forms of balance.
Value balance
How much of the portfolio is focused on cost reduction, revenue growth, resilience, compliance, capability building and strategic options?
Horizon balance
How much investment produces near-term returns versus longer-term capability?
Risk balance
Are multiple initiatives exposed to the same technology, supplier, regulatory assumption or market dependency?
Capacity balance
Do several projects require the same scarce people, assets or change windows?
Reversibility balance
How much capital is committed to difficult-to-reverse choices compared with staged or option-like investments that preserve flexibility?
These dimensions expose risks that project-by-project scoring cannot.
Opportunity Cost Is the Missing Line in Most Business Cases
A business case usually describes the cost of doing an initiative and perhaps the cost of doing nothing. It rarely states the value of the best alternative initiative that will be delayed or unfunded.
Yet that is the essence of portfolio choice.
Suppose a manufacturer can fund either an automated production cell or a digital customer configuration platform. Both have plausible returns. The automation may reduce labour and improve consistency; the digital platform may accelerate quotation, reduce engineering effort and change the customer experience. The decision is not whether both are “good”. It is which commitment best advances the strategy under present constraints.
The opportunity cost may also be capability rather than cash. The same engineering team may be essential to both initiatives. Funding both can reduce the probability that either succeeds.
The Value of Portfolio Diversity
The source matrix provides a useful prompt for portfolio design. Stable improvement projects can fund and strengthen the core. Higher-value initiatives using proven technology can extend competitive advantage. More uncertain innovation can create future strategic options.
The important point is not to target a fixed percentage in each category. There is no universal balance.
A regulated utility, defence organisation, software company and medical device manufacturer face different tolerances for uncertainty. Portfolio structure should follow enterprise strategy, risk appetite, cash position and capability.
What matters is that the composition is deliberate.
White Elephants and the Governance of Exit
The source material describes “white elephants” as projects that once showed promise but are no longer viable. That category deserves more attention than it usually receives.
Projects accumulate sunk costs, sponsors, teams and reputational commitment. These create pressure to continue even after the original assumptions weaken.
A governance system should therefore require evidence not only to start an initiative but to continue it.
Decision gates should ask:
- Has strategic relevance changed?
- Are expected benefits still material?
- Has cost-to-complete changed sufficiently to alter the investment decision?
- Is the solution still technically or commercially preferable?
- Has another initiative become a better use of the same capacity?
- What would we do if the project had not already consumed money?
This makes termination a controlled investment decision rather than a crisis.
Decision Framework
A practical portfolio review can use four layers.
Layer 1 — Minimum viability. Eliminate initiatives that fail mandatory legal, ethical, strategic or feasibility tests.
Layer 2 — Comparative attractiveness. Compare strategic contribution, expected benefits, whole-life cost, risk and time to value.
Layer 3 — Portfolio interaction. Examine dependencies, shared resources, change saturation, risk concentration and sequencing.
Layer 4 — Portfolio resilience. Test the proposed portfolio against scenarios: lower revenue, supplier failure, regulation, technology delay, labour shortage or executive capacity constraints.
The output should not be a ranking alone. It should be a set of decisions: accelerate, maintain, redesign, defer, hold for capacity, stop or investigate further.
From Strategy to Execution
Immediately, portfolio reviews should display resource bottlenecks and dependencies alongside cost and schedule status. A project shown as “green” while consuming a critical capability required elsewhere is not fully green.
In the medium term, investment governance should define explicit capacity envelopes. These might include engineering hours, implementation teams, operational shutdown windows, data migration capacity or number of major changes a business unit can absorb at once.
Over the long term, organisations should develop portfolio archetypes linked to strategy. A business in harvest mode should not have the same portfolio shape as one pursuing expansion, technological renewal or resilience.
The portfolio should express strategy through committed resources, not merely through labels attached to projects.
Signals to Monitor
Watch for persistent over-allocation of the same specialists, a growing backlog of approved-but-not-started projects, projects waiting on each other without explicit sequencing, benefits that depend on the same uncertain market assumption, and “temporary” resource workarounds becoming permanent.
Another important signal is strategic monotony. If nearly every project has the same value proposition—cost reduction, for example—the portfolio may be neglecting growth, resilience or capability even if every individual business case is rational.
Questions for the Leadership Team
- What strategic role does each major initiative play in the portfolio?
- Which portfolio risks are concentrated across several projects?
- What would we stop if a 20 per cent capacity reduction occurred tomorrow?
- Which projects are waiting for resources that are already committed elsewhere?
- Are we protecting enough capacity for future opportunities rather than filling every available slot?
- Which current initiative has become a white elephant but remains politically difficult to challenge?
Closing Perspective
Prioritisation is not the act of calling valuable projects important. It is the act of choosing among competing valuable uses of scarce resources.
The strongest portfolio leaders are therefore willing to create visible trade-offs. They recognise that funding everything attractive can reduce overall enterprise value, and that disciplined deferral or termination may be as strategically important as launching the next project.