The purpose of project selection is not to approve every initiative that can justify itself; it is to allocate scarce organisational capacity to the combination of investments that best advances strategy.
A project can have a positive business case and still deserve rejection.
That statement feels uncomfortable because project approval is often framed as an individual test. If the initiative is strategically aligned, feasible and expected to create value, why would leaders not proceed?
Because the organisation does not invest one project at a time in isolation. It invests a portfolio.
The supplied project-selection material emphasises strategic alignment, resource constraints, selection criteria, portfolio balance and the strategic risks of accepting or rejecting projects. It also presents a selection process with multiple outcomes: abandon, request more information, reject, hold for resources, accept and assign resources.
That is a more realistic model than a simple approve-or-reject gate.
Project selection is therefore a capital-allocation discipline. Capital includes money, but also skilled people, executive attention, technology capacity, change tolerance and operational bandwidth.
The Strategic Context
Every organisation faces more potential work than it can execute well.
Ideas emerge from customers, regulation, technology, improvement opportunities, asset needs, market shifts and executive priorities. Some will be compelling. Many will be individually defensible.
The portfolio question is different:
Which combination of initiatives creates the strongest strategic value within our constraints?
The supplied study material links project selection to corporate strategy and describes operational budgets as focused on efficiency while capital investments support future effectiveness and growth. It also notes that not-for-profit organisations face fixed funding constraints and must choose projects that improve outcomes or advance strategic and political goals.
Across both contexts, the common problem is scarcity.
What Leaders Commonly Misread
The first misreading is that strategic alignment is enough.
If ten projects all align with strategy but the organisation can execute only five, alignment does not resolve the choice.
The second is that ranking projects by one financial metric creates an objective portfolio.
Financial measures are useful, but the sources also emphasise technical feasibility, risk, strategic fit and resource constraints. A portfolio made entirely of the highest-return projects may create excessive concentration in one capability, market, technology or risk type.
The third is that rejecting a good project destroys value.
Sometimes rejection protects greater value elsewhere. Approving a project consumes resources that cannot be used for another opportunity. That sacrificed alternative is the opportunity cost of the decision.
Reframing the Issue
Portfolio selection should move through three questions.
Is the project good enough?
This is the individual hurdle. Does the proposal have strategic relevance, acceptable feasibility, justified benefits and manageable risk?
Is it better than the alternatives?
This is the comparative hurdle. Given competing proposals, which creates greater value for the resources consumed?
Does it improve the portfolio?
This is the system hurdle. Does adding the project create an acceptable overall balance of risk, return, timing, dependencies and capability demand?
A project can pass the first test and fail the second or third.
Strategic Alignment Must Be Specific
The source material places project selection downstream from mission, external and internal analysis, goals and strategic choices.
That hierarchy matters because “aligned to strategy” is often used too loosely.
A project is not meaningfully aligned simply because its sponsor can attach it to a broad corporate objective. Leaders should be able to explain:
- which strategic outcome the project advances;
- how much contribution is expected;
- when the contribution is likely to appear;
- what must be true for the benefit to occur;
- and what other strategic work competes for the same resources.
This turns alignment from narrative to comparative evidence.
Portfolio Balance and the Risk-Return Mix
The supplied Gray and Larson-style matrix groups projects by technical feasibility and commercial potential into four categories commonly labelled bread-and-butter, pearl, oyster and white elephant.
The labels are less important than the underlying principle.
A healthy portfolio may need a mix of dependable improvement initiatives and more uncertain future-facing bets. If all investment goes to low-risk incremental work, the organisation may protect current performance while starving future growth. If too much goes to high-uncertainty innovation, near-term performance and delivery reliability may deteriorate.
Portfolio leadership is therefore an exercise in balance, not merely ranking.
Capacity Is a Strategic Constraint
The source notes explicitly ask what resource constraints the organisation has and what resources it is willing to make available.
This is often the decisive portfolio issue.
Two projects may both require the same specialist engineering team, data platform, procurement capability or executive sponsor. Approving both does not double capacity. It creates hidden competition.
When this competition is ignored, the consequences appear later as delays, burnout, quality problems and repeated reprioritisation.
The portfolio was overcommitted before the projects underperformed.
The Portfolio Should Include the Cost of Delay
Deferral is not neutral.
When a proposal is held because resources are unavailable, the organisation should understand what delay costs. For some initiatives, waiting has little consequence. For others, delay can increase regulatory exposure, lose market opportunity, extend inefficient operations or allow asset condition to deteriorate.
This creates a useful distinction between project value and value of timing.
An initiative with moderate total value but a rapidly closing opportunity window may deserve priority over a larger but more patient investment. Conversely, a proposal with strong long-term economics may reasonably wait if the cost of delay is low and scarce capability is required elsewhere.
Portfolio sequencing should therefore consider not only “how valuable?” but also “how time-sensitive?”
Dependencies Can Make Individual Rankings Misleading
Projects rarely operate independently.
One initiative may create infrastructure required by several others. Another may depend on a data platform that is not yet available. Two projects may compete for the same shutdown window or specialist team. A regulatory project may be mandatory before a commercial expansion can proceed.
This means the best individual ranking can produce a poor portfolio sequence.
Portfolio leaders should identify enabling, dependent and mutually constraining relationships before final allocation. In some cases, a lower-return enabling project deserves earlier funding because it unlocks greater portfolio value.
The relevant unit of optimisation is therefore not always the project. It may be a group of interdependent investments.
Decision Framework
A useful selection model can evaluate each candidate across six lenses:
| Lens | Question |
|---|---|
| Strategic contribution | How materially does this advance a priority outcome? |
| Value | What benefits justify the investment and disruption? |
| Feasibility | Can it be delivered and adopted under realistic conditions? |
| Risk | What downside or uncertainty does the organisation accept? |
| Capacity | What scarce resources and executive attention will it consume? |
| Portfolio effect | What concentration, dependency or opportunity cost does it create? |
The decision should then allow more than approve or reject.
Possible outcomes include:
- approve now;
- approve subject to conditions;
- defer until capacity is available;
- request more evidence;
- redesign the proposal;
- combine with another initiative;
- reject;
- terminate an existing lower-value initiative to release capacity.
The last option is often overlooked. Portfolio optimisation requires the courage to stop as well as start.
Related article: The Business Case Is a Governance Instrument, Not an Approval Form
From Strategy to Execution
Immediate action: require every investment proposal to identify the scarce capabilities it will consume and the initiatives it is likely to compete with.
Medium-term capability: create a portfolio review that considers projects together. Use common selection criteria, but retain judgement for differences in strategic role and risk.
Long-term positioning: build dynamic reallocation into governance. Projects should not retain funding indefinitely simply because they were once approved. When evidence changes, the portfolio should be able to redirect resources.
That is how strategy becomes an active allocation process rather than an annual planning document.
Signals to Monitor
Portfolio leaders should be concerned when:
- almost every proposal is approved;
- projects are prioritised independently by different functions;
- the same specialist resources appear critical across many schedules;
- strategic alignment scores are uniformly high;
- low-value legacy projects remain protected because stopping them is politically difficult;
- new projects are added without removing or delaying existing commitments;
- portfolio reviews focus on status reporting rather than allocation decisions;
- projects with weakening business cases continue automatically.
These signals suggest the organisation is managing a list of projects rather than a portfolio of investments.
Questions for the Leadership Team
- Which current projects would we not start if we were making the decision today?
- What opportunity are we giving up by funding this initiative?
- Which scarce capabilities are overloaded across the portfolio?
- Are we over-concentrated in one technology, market, benefit type or risk category?
- Which projects protect today's performance, and which create future capability?
- What evidence would cause us to defer or stop an already approved project?
- Does the portfolio reflect our stated strategy, or merely the history of past approvals?
Closing Perspective
Good project selection is not a contest to identify the highest-scoring proposal.
It is a disciplined choice about where the organisation will place finite capital, capability and leadership attention while accepting that other attractive opportunities must wait or be rejected.
The quality of the portfolio therefore depends as much on what leaders refuse to fund as on what they approve.