Skipping resource levelling in a multi-project environment causes a predictable chain of damage: shared specialists become overloaded, projects queue behind one another, and delays compound across the whole portfolio. The harm is not confined to individual schedules. It spreads through every initiative that competes for the same people, and the cost accumulates silently until it shows up as missed quarters and stalled value. The questions below trace exactly how that damage unfolds and what a more complete response looks like.
What actually causes the damage when resource levelling is skipped?
The damage starts the moment a shared specialist is assigned to more projects than she can serve at once. Each project claims her as a priority, so she switches between them. Every switch costs time, and every project waits. The waiting is invisible in project reports, but the clock on each initiative keeps running, and value keeps being deferred.
The structural cause is a mismatch between demand and capacity that nobody has made explicit. When an organisation starts projects based on budget availability rather than resource capacity, it creates a queue it cannot see. The queue is not in any plan. It lives in the schedules of the people who carry every initiative simultaneously.
Two patterns tend to accelerate the damage:
- Work in progress rises without limit, so each specialist serves more projects than she can advance meaningfully in any given week.
- The order in which projects receive attention is decided by whoever argues loudest, not by which project produces the most value from the next available hour of constrained capacity.
Neither pattern appears on a status dashboard. Both determine what the portfolio actually earns.
How does ignoring resource levelling create project delays?
Ignoring resource levelling creates project delays through a mechanism called resource contention. When the same specialist is needed by four projects at once, each project advances only when she is available. The other three wait. Because each project reports its own status independently, the waiting time rarely appears as a delay in any single report. It appears as slippage at the end, when deadlines are missed.
The delay is not caused by poor planning within any individual project. The plans may be perfectly sound. The delay is caused by the interaction between projects once they share the same people. A project that looks on track in isolation is already accumulating hidden wait time the moment its critical path passes through an overloaded specialist.
This is why adding more governance to individual projects rarely shortens delivery times at the portfolio level. The bottleneck is not in the projects. It is in the shared resource system that sits between them.
What are the hidden costs of poor resource levelling at the portfolio level?
The hidden costs of poor resource levelling are the economic consequences of delay that never appear in a project budget. Every day a value-generating initiative is held up by a resource constraint is a day its intended return is not being earned. Stephen Devaux formalised this idea through the concept of drag cost: the cost imposed on a project by any element on the critical path that extends its duration. When a shared specialist is on the critical path of multiple projects, her unavailability imposes drag cost on every one of them simultaneously.
At the portfolio level, these costs stack. A specialist shared across four delayed projects is not causing one delay. She is causing four, each with its own drag cost running in parallel. The total economic loss is rarely calculated because organisations account for project costs, not for the cost of time lost waiting for constrained resources.
A related measure, also credited to Devaux, is the DIPP (Devaux's Index of Project Performance), which connects remaining project value to remaining cost and time. When resource contention extends duration, the DIPP deteriorates even when the project appears to be under budget, because the expected value at completion is shrinking relative to the investment still required.
These hidden costs are the reason portfolio underperformance persists even in organisations with strong project disciplines. The loss is real, but it is priced nowhere.
Why does strong project management fail to fix resource levelling problems?
Strong project management fails to fix resource levelling problems because it operates at the wrong level. A project manager's responsibility is to deliver her project. She optimises within that boundary. She cannot optimise across the boundary, because the decisions about how shared resources are allocated between projects sit above her authority and outside her visibility.
This is what Flow Economics calls the Project Illusion: the belief that if individual projects are well planned, well governed, and delivered on time, the organisation will perform well. The belief is coherent at the project level and wrong at the portfolio level. Portfolio performance depends on how projects interact when they compete for constrained resources, not on how well each project is managed in isolation.
Investing in better project delivery methods, more detailed scheduling, or tighter governance does not resolve this. It improves performance within each project's boundary while leaving the interactions between projects unmanaged. The constraint is structural, and structural problems require a structural response.
What's the difference between resource levelling and managing portfolio flow?
Resource levelling and managing portfolio flow address related problems at different levels of abstraction. Resource levelling is a scheduling technique: it adjusts the timing of tasks to avoid overloading individual resources, typically within a single project or a defined set of projects. It smooths the demand curve against available capacity. Resource smoothing is a closely related technique that adjusts task timing within existing schedule constraints rather than extending them, making it less disruptive but also less powerful when genuine overloads exist.
Managing portfolio flow goes further. It treats the entire portfolio as an economic system with a constraint, usually a small group of specialists whose capacity limits what the whole system can produce. The question is not only how to avoid overloading those specialists. It is which projects should receive their attention first, in what order, and at what cost to the portfolio if the sequence is wrong.
The distinction matters because resource levelling can be applied project by project, leaving the interactions between projects unaddressed. Portfolio flow management requires a view across all active initiatives simultaneously, with sequencing decisions guided by the economic value of each project and the cost of delay, not by schedule convenience or sponsor influence.
In the Flow Economics Maturity Model, resource levelling sits at level two or three: it improves individual project schedules and brings some structure to the portfolio, but it does not yet make the constraint visible or let economic value guide the order of work. Levels four through six are where flow management begins: seeing the constraint, letting it set the sequence, and eventually pricing every hour of constrained capacity against the return it generates.
When should organisations address resource levelling as a portfolio problem?
Organisations should address resource levelling as a portfolio problem as soon as they are running more projects than their shared specialists can carry without switching between them. In practice, this threshold is crossed earlier than most leaders recognise. The signal is not a formal capacity report. It is the pattern of projects that are individually on track but collectively late, of delivery timelines that slip without a clear cause, and of specialists who are always busy but whose busyness never seems to translate into finished work.
The right moment to reframe the problem is when additional investment in project management methods stops improving portfolio outcomes. At that point, the constraint is not in how projects are run. It is in how the shared resource system between them is governed, sequenced, and priced.
Specific conditions that signal the need to act at the portfolio level include:
- The same small group of specialists appears on the critical path of multiple active projects.
- Project completion dates are routinely revised without a clear explanation of what caused the slippage.
- Portfolio sequencing decisions are made by whoever argues most persuasively rather than by any economic logic.
- No one has calculated what a month of delay costs for the organisation's highest-value initiatives.
When these conditions are present, resource levelling as a scheduling technique is not enough. The organisation needs a way to see the shared resource system as a whole, to understand what its constraint is costing, and to make sequencing decisions based on economic value rather than political weight.
How Flow Economics helps with resource levelling in multi-project environments
Flow Economics provides a framework for exactly the layer that resource levelling techniques leave unaddressed: the shared resource system where competing project demands meet constrained specialist capacity. Rather than treating resource levelling as a scheduling exercise, Flow Economics makes the constraint visible, attaches an economic cost to delay, and gives portfolio leaders a basis for sequencing decisions grounded in value rather than seniority.
In practical terms, the framework helps by:
- Identifying which shared specialists are acting as the system constraint and what their unavailability is costing the portfolio.
- Applying drag cost and DIPP thinking to quantify the economic impact of delay at the portfolio level, not just within individual projects.
- Shifting sequencing decisions from political negotiation to an economic logic: the constraint's next available hour goes to the project that earns the most from it.
- Giving leaders a simulator to test sequencing and capacity decisions before applying them in the real organisation.
If you lead a PMO, portfolio, or transformation function and recognise the patterns described here, the Flow Economics course introduces the framework through video lessons, workbooks, and a working portfolio simulator. The first two modules are free. If you would prefer to discuss how the framework applies to your specific situation, you can get in touch directly.