When everything is authorised, the organisation has not prioritised; it has distributed scarcity across too many commitments.
A familiar pattern appears in overloaded organisations. Projects are late. Specialist resources are shared across too many initiatives. Managers spend their days resolving conflicts. New work is added because it is urgent, regulatory, customer-driven or sponsored by an executive. The response is often to improve scheduling.
Scheduling can expose the collision. It cannot decide which commitments should no longer exist.
The supplied EY portfolio-management paper identifies too many simultaneous projects, overlapping initiatives, excessive "must have" work, ineffective prioritisation and lack of organisational capacity to absorb change as recurring portfolio challenges. It links these problems to delayed benefits, inefficient resource allocation, extended timelines and weak execution.
This is an executive commitment problem before it is a project-control problem.
The Strategic Context
Organisations have finite throughput for change.
That throughput depends on more than the number of project managers available. It includes engineering capacity, business subject-matter experts, procurement, technology teams, operational leaders, decision-makers, customers, regulators and the ability of frontline staff to absorb new processes.
When leadership commits more work than the system can absorb, projects slow each other down.
People multitask. Decisions queue. Dependencies wait. Testing environments become bottlenecks. Operations cannot release staff for implementation. Sponsors divide their attention.
The result can look like widespread project-management weakness even when each team is behaving rationally inside an overloaded system.
What Leaders Commonly Misread
The first mistake is believing capacity can be solved by asking teams to "work smarter". Productivity improvements may help, but they do not remove the need to choose when demand structurally exceeds supply.
The second is adding contingency to every project independently. If all projects depend on the same constrained resource, individual contingencies do not create more capacity.
The third is confusing urgency with priority. Many initiatives may be urgent. Priority is the relative order in which scarce resources should be committed.
The fourth is assuming delayed projects prove weak project managers. Sometimes delay is the predictable consequence of executives approving more simultaneous work than the organisation can execute.
Reframing the Issue
Portfolio overload should be treated as a system constraint.
The key question is not:
How can every project stay on schedule?
It is:
What combination of commitments can the organisation execute without destroying flow, benefit timing and operational stability?
That change in framing moves leadership from local optimisation to portfolio throughput.
Related article: Capacity Is a Strategic Constraint: Match Ambition to What the Organisation Can Absorb
How Overload Destroys Value
It increases work in progress
More active projects create more handovers, more coordination, more meetings and more competing demands.
Progress can actually slow as activity increases.
It delays benefits
A project that starts early but waits repeatedly for resources may realise value later than a project deliberately deferred and then executed with focus.
It creates hidden prioritisation
When leaders refuse to prioritise formally, scarce teams prioritise informally. The loudest sponsor, most urgent escalation or most visible deadline receives attention.
The organisation still prioritises, but without enterprise logic.
It weakens quality of decision-making
Executives with too many major initiatives cannot give each one adequate sponsorship. Decisions are delayed or delegated without clear authority.
It increases change saturation
Operational teams can absorb only so much concurrent change. Even well-designed initiatives can fail if implementation demand exceeds the organisation's ability to learn and adapt.
Decision Framework
A practical portfolio overload review has four steps.
1. Identify the binding constraints. Which resources or organisational conditions genuinely limit throughput?
2. Measure portfolio demand on those constraints. Do not rely only on project headcount. Identify when each initiative needs the scarce resource and at what intensity.
3. Compare demand with credible capacity. Avoid theoretical availability. Capacity must account for business-as-usual work, leave, operational peaks and decision latency.
4. Change commitments. Sequence, defer, stop, redesign or reduce scope until the portfolio is executable.
The fourth step is the one organisations often avoid.
Without it, capacity analysis becomes another report documenting a problem leadership has chosen not to solve.
From Strategy to Execution
Immediately, identify the top three cross-portfolio bottlenecks. Examples might include a small engineering team, cyber-security review, operational subject-matter experts or executive approval.
In the medium term, create portfolio-level resource and change-capacity views that show conflicts before projects are fully committed.
Longer term, incorporate capacity into strategy formation. A strategy that requires capabilities the organisation cannot deploy is not yet an executable strategy. Leaders may need to build new capability, simplify the change agenda or sequence ambition over a longer horizon.
Related article: Portfolio Management Is Capital Allocation in Action
Signals to Monitor
Watch for increasing numbers of paused tasks inside active projects; the same names appearing as critical resources across many initiatives; frequent rescheduling caused by resource availability; operational teams receiving multiple competing implementations; executives repeatedly escalating "their" projects; and benefit dates sliding even when individual project budgets remain stable.
A particularly strong signal is rising project count without a corresponding increase in completed strategic outcomes.
Questions for the Leadership Team
- What is the current binding constraint on our change portfolio?
- Which projects are active mainly because no one has made the decision to defer them?
- Are we measuring resource demand at the portfolio level or trusting each project plan independently?
- Where has informal sponsor power replaced explicit prioritisation?
- What would happen to benefit timing if we ran fewer initiatives with greater focus?
- Which capabilities should we build because they are persistent strategic constraints?
Closing Perspective
Overload is not evidence that the organisation is ambitious. It is evidence that ambition has not been converted into choices.
The discipline of strategy is exclusion. The discipline of portfolio management is making that exclusion operational.
When commitments exceed capacity, the answer is not another schedule. It is a decision about what the organisation will not do now.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.