When every project is a priority, scarce capability is divided across too much work and the portfolio delays value everywhere.
Organisations often approve projects individually and discover capacity collectively. Each business case appears affordable. Each sponsor secures some access to the same engineers, analysts, commercial specialists, technology teams and executives. Resource plans show partial allocations that add neatly to 100 per cent.
Execution feels different. People switch between urgent requests, meetings and technical contexts. Work waits for review. Decisions queue behind the same authority. Projects report local delays while the portfolio continues to release more work.
The resulting cost is rarely visible in one budget. It appears as extended duration, lost focus, lower quality, delayed benefits and exhausted specialists.
The Strategic Context
Traditional critical-path analysis emphasises task dependencies. Critical-chain thinking adds resource dependencies and the effect of shared constraints. At portfolio level, this becomes a question of organisational capacity: how many initiatives can the enterprise execute concurrently without reducing flow?
UK government portfolio guidance similarly emphasises directing and sustaining portfolios rather than treating them as collections of independent projects. Capacity, risk profile and strategic priority must be considered across the whole investment system.
The key distinction is between resource utilisation and value flow. A specialist can appear fully utilised while several important deliverables wait. High utilisation of a constrained resource often increases queues and lengthens lead time.
What Leaders Commonly Misread
The first misreading is that splitting a person across four projects gives each project 25 per cent capacity. Availability is not equivalent to productive flow. Context switching, competing meetings, hand-offs and re-establishing technical understanding consume time.
The second is that every project should start as soon as approved. Starting creates work in progress. It does not create completion. Releasing more initiatives than the organisation can absorb increases queues and reduces the speed at which benefits arrive.
The third is that resource problems belong to project managers. A project manager can sequence assigned work but cannot resolve enterprise overcommitment when several sponsors hold legitimate claims on the same capability.
The fourth is that local schedule recovery improves portfolio performance. Moving a specialist to the loudest project can protect one milestone while delaying a more valuable or less reversible commitment.
Reframing the Issue
Portfolio capacity should be governed as a flow system.
Demand enters as projects, changes and operational work. Capacity is provided by teams, suppliers, facilities and decision authorities. Constraints limit throughput. When demand exceeds effective capacity, queues grow.
The portfolio decision is therefore not only which projects deserve funding. It is which projects should be active now, which should be sequenced later and which should stop.
This reframing exposes opportunity cost. A project is not free to start merely because its direct budget is available. It may consume the constraint that determines completion elsewhere.
Related article: Why the Iron Triangle Is Too Narrow for Executive Project Control
Identify the Real Constraints
Headcount alone is a poor measure of capacity. Ten generalists do not replace one authorised specialist at a critical interface.
Common portfolio constraints include:
- systems engineers and technical authorities;
- estimators, schedulers and commercial specialists;
- cybersecurity, safety or quality assurance;
- commissioning resources;
- procurement and legal review;
- data and integration environments;
- executive decision forums;
- external regulators and customers; and
- suppliers serving multiple initiatives.
Some constraints are persistent; others move by phase. Portfolio plans should show when each initiative demands the constraint, not merely its average allocation across a year.
Context Switching Creates Invisible Queues
Multitasking is often defended as flexibility. At modest levels, it can help use gaps productively. At high levels, it fragments attention and encourages local priority changes.
The hidden effects include:
- restart time after interruption;
- greater hand-off and coordination demand;
- slower feedback;
- increased error and rework;
- decisions made with partial context;
- priority escalation as the normal route to service; and
- reduced capacity for learning and improvement.
The organisation then interprets slow completion as a need to start earlier, which increases work in progress and strengthens the cycle.
Protect the Constraint, Not Every Local Plan
Critical-chain concepts use buffers and sequencing to protect constrained flow. At portfolio level, the principle is more important than any particular formula.
Leaders should:
- limit the number of initiatives drawing heavily on the constraint;
- ensure work arriving at the constraint is ready;
- prevent avoidable interruptions and priority changes;
- maintain visibility of the queue;
- direct improvement effort to the constraint; and
- avoid optimising non-constrained teams in ways that create more upstream inventory.
A design team producing drawings faster than assurance can review them may appear productive while the system accumulates unverified work. The portfolio benefits more from improving review flow than maximising design starts.
Buffers Need Governance
Buffers can protect delivery from uncertainty, but they must not become unexamined padding. A project buffer can protect final completion. A feeding buffer can protect critical work from a converging path. A capacity buffer can preserve the ability to respond to urgent or uncertain demand.
Leadership should define:
- what the buffer protects;
- who can consume it;
- what signals trigger intervention;
- whether consumption reflects normal variation or a systemic problem; and
- how protection is replenished or redesigned.
Buffer status can be a more useful management signal than whether every individual task met its local date.
Decision Framework
| Portfolio question | Decision implication |
|---|---|
| What capability constrains flow? | Focus planning and improvement on the true bottleneck |
| Which initiatives consume it, and when? | Sequence demand rather than average allocations |
| What value is delayed in the queue? | Prioritise by enterprise consequence, not sponsor volume |
| What work can be paused safely? | Reduce work in progress and protect reversibility |
| What should be stopped? | Release capacity from weak or obsolete investments |
| What buffer is required? | Protect high-value commitments from expected uncertainty |
Priority should be explicit enough to resolve conflict before every issue becomes an escalation.
Related article: When a Project Falls Behind, Compression Is a Business Decision
From Strategy to Execution
Immediate action: Identify the five capabilities most frequently shared across active initiatives. Map demand, queues, wait times and priority conflicts.
Medium-term capability: Introduce portfolio-level capacity planning, work-in-progress limits and readiness criteria. Do not allow an initiative to consume constrained capacity merely because its funding has been approved.
Long-term positioning: Develop or acquire capability where the strategic pipeline justifies it. Capacity investment should target persistent constraints, while portfolio governance continues to challenge demand.
Signals to Monitor
- Specialists attend many projects but complete few critical outputs.
- Projects wait longer for review than work takes to perform.
- Priority changes occur weekly.
- Sponsors secure resources through escalation rather than portfolio decisions.
- New initiatives start while older high-value work remains blocked.
- Overtime is chronic at the same capability.
- Resource plans show high utilisation but benefit delivery continues to slow.
Questions for the Leadership Team
- Which capability currently determines portfolio throughput?
- How much high-value work is waiting for that capability?
- Which active initiative should not have started yet?
- What project should be paused or stopped to release capacity?
- Are we prioritising value or responding to the loudest escalation?
- What buffer protects the portfolio from predictable urgent demand?
- Where would a capability investment remove a persistent strategic constraint?
Closing Perspective
Multitasking is not merely a personal productivity problem. At enterprise scale, it is often evidence that investment approval and organisational capacity have become disconnected.
Portfolio leadership requires the courage to sequence, pause and stop. The objective is not to keep every project moving. It is to complete the most valuable change with the least avoidable waiting—and then release capacity for what should come next.
About the author
Kevin Jogin is Founder & Principal Advisor at EraNorth. Meet the Founder.