Too Many Good Projects Is a Portfolio Failure

A portfolio fails when it approves more good work than the enterprise can execute well, even if every individual business case appears reasonable.

Most portfolio overload does not begin with obviously bad projects. It begins with good ideas, credible sponsors and benefits that look attractive in isolation. The failure occurs when too many of them are approved against the same finite people, capital, systems and executive attention.

Many organisations recognise the symptom but misdiagnose the decision underneath it. The enterprise then pays for delay, multitasking, dependency conflict and weak benefits while each initiative continues to defend its own local logic. That distinction matters because the wrong framing can produce competent execution of a strategically weak choice.

The Strategic Context

The portfolio source material emphasises strategic alignment, selection, balancing and risk-informed decision-making. Its strongest executive implication is that the portfolio is a system of competing investments, not a container for every approved project.

At enterprise level, the portfolio must translate strategy into a limited set of funded commitments. At portfolio level, selection needs to account for opportunity cost, balance, risk concentration and capacity. At program or transformation level, related projects should be grouped where shared outcomes and dependencies make separate governance misleading. From a systems perspective, adding work increases queues and coordination load non-linearly when shared constraints become saturated. These lenses prevent a narrow solution from being mistaken for a complete strategy.

What Leaders Commonly Misread

Every positive business case deserves approval. A project can be valuable and still be less valuable than the opportunity it displaces. Relative value matters more than stand-alone attractiveness.

Capacity is a delivery problem. If leadership approves more work than the system can absorb, the overload is created at portfolio level. Execution teams cannot schedule their way out of structural overcommitment.

Stopping is failure. Terminating or deferring lower-value work can protect strategy and release scarce capability. A healthy portfolio makes stopping normal.

Reframing the Issue

Portfolio management is the discipline of choosing the best combination of investments under constraint. That means asking what the enterprise will not fund, which work must be sequenced and how much change the organisation can absorb without degrading delivery and operations.

For portfolio prioritisation, a stronger framing is to ask three questions together: what outcome matters, what constraint governs that outcome, and what evidence would justify changing course. That moves management away from defending a preferred solution and toward managing a decision. It also makes opportunity cost visible: every commitment of capital, scarce capability or executive attention displaces something else.

Strategic Analysis

Opportunity Cost Must Be Visible

The true cost of an initiative includes the better initiative that cannot proceed because the same engineers, data teams, capital or decision forums are already committed. Traditional business cases often hide this because they evaluate projects one at a time.

Portfolio decisions need comparative value and constraint information. This can force sponsors to compete on enterprise value rather than local urgency.

Overload Creates Systemic Delay

When too many initiatives share scarce capability, work starts earlier but finishes later. People switch context, dependencies queue and decisions wait for overloaded specialists or executives. Progress reporting can still show widespread activity while throughput declines.

Limiting work in progress can increase completion and benefits even though fewer projects are active. Politically, starting less work can look slower before the system demonstrates faster completion.

Balance Is More Than Risk Diversification

A portfolio needs a deliberate mix across horizons, strategic themes, mandatory work, growth, productivity and capability. Balance also means avoiding concentration on the same assumptions, suppliers, technologies or people.

Several individually diversified projects can still create a correlated enterprise exposure. Mandatory work can crowd out strategic renewal unless its demand on capacity is forecast explicitly.

Stop Decisions Create Capacity

Projects should continue only while their strategic justification, evidence and relative priority remain strong. When assumptions weaken or higher-value needs emerge, stopping protects future value.

Portfolio governance needs review points that can genuinely reduce commitment. Sunk cost, sponsor reputation and fear of admitting error often keep weak initiatives alive.

The Enterprise Test in Practice

Consider a hypothetical multi-program enterprise facing a material decision about portfolio prioritisation. The leadership team deliberately avoids beginning with a preferred solution. Instead it tests strategic contribution, relative value and constraint demand as separate questions. That changes the discussion because the team must compare the intended outcome with the constraint, evidence and exposure surrounding it. The familiar assumption that every positive business case deserves approval becomes visible as an assumption rather than an operating truth.

The team then defines a bounded decision rather than a permanent commitment. It agrees what evidence will be reviewed, which trade-off is being accepted and what would justify a different path. Two signals receive particular attention: Rising active-project count, because new work starts faster than existing work finishes., and Shared-resource queues, because critical specialists or decision-makers are committed across too many initiatives.. Neither signal is treated as a dashboard decoration. Each is linked to a management conversation about whether the original logic still holds and whether additional capital, capacity or organisational disruption remains justified.

At scale, this way of working changes more than the immediate decision. It creates a repeatable habit of distinguishing commitment from evidence and local optimisation from enterprise consequence. The value is not that every uncertainty disappears. The value is that leaders can see where uncertainty sits, which part of the system carries it and how quickly they can adapt before the cost of reversal rises. That is how portfolio prioritisation moves from a specialist topic into an executive management capability.

Decision Framework

A useful framework should make judgement more disciplined without pretending that judgement can be automated. For portfolio admission and continuation, leaders should test the following criteria before committing further resources:

Strategic contribution: Which explicit strategic outcome does the initiative advance, and how material is that contribution?
Relative value: What higher-value work would be delayed or displaced if this initiative proceeds?
Constraint demand: Which scarce capabilities, systems, suppliers or executive decisions will it consume?
Risk concentration: Does it increase exposure to assumptions or dependencies already concentrated elsewhere in the portfolio?
Exit logic: What evidence or change in context would justify defer, redesign or termination?

For portfolio prioritisation, the criteria should be considered together. A proposal can be attractive on one dimension and still be unacceptable overall. Where evidence is weak, the answer is not automatically to reject the proposal; it may be to reduce the commitment, run a bounded experiment, create a review gate or preserve an exit route. Reversibility is itself a strategic asset.

From Strategy to Execution

Immediate action. Create a single view of active initiatives against the organisation’s true constrained capabilities and identify where demand exceeds supply. The purpose of the first move is to improve the quality of the next decision, not to create the appearance of momentum.

Medium-term capability. Move portfolio governance from annual ranking to regular rebalance, with explicit stop, defer and accelerate decisions. This is where governance, data, routines and ownership need to become repeatable rather than dependent on a few capable individuals.

Long-term positioning. Develop an enterprise investment system in which strategy, capacity, benefits and risk data are integrated before projects are authorised. Over time, the organisation should be able to make the decision faster, with better evidence and lower coordination cost. That is a capability advantage, not simply a process improvement.

Signals to Monitor

For portfolio prioritisation, leading indicators matter because financial or delivery outcomes often become visible only after choices are expensive to reverse. Monitor:

Rising active-project count — new work starts faster than existing work finishes.
Shared-resource queues — critical specialists or decision-makers are committed across too many initiatives.
Milestone slippage across unrelated projects — the common cause may be portfolio overload rather than local project failure.
Benefits dilution — projects deliver outputs but operational teams cannot absorb or exploit them.
No termination history — the portfolio almost never stops work despite changing assumptions and priorities.

Questions for the Leadership Team

Which active project would we not approve if it came to us for the first time today?
Where is the same scarce capability promised to multiple initiatives?
What are we delaying by keeping our lowest-value project alive?
How many changes can our operating teams absorb simultaneously?
Which projects are individually sound but collectively incompatible?

Related article: Portfolio Capacity: The Constraint Strategic Plans Rarely Show
Related article: Stop, Defer or Accelerate: How Leaders Should Rebalance a Portfolio
Related article: Strategy Is a System of Choices, Not a List of Initiatives

Closing Perspective

Portfolio leadership is not the art of finding room for every good idea. It is the discipline of preserving enough focus and capacity for the best ideas to finish, become adopted and create value.

The leadership responsibility is therefore not to maximise activity around portfolio prioritisation. It is to make the underlying choice explicit, govern the assumptions, protect the enterprise from avoidable downside and direct scarce capacity toward the outcomes that matter most. That is the difference between managing a topic and leading a system.

About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.