A new field for portfolio decision-making.
For decades, the management of multiple projects has been treated as an extension of project management. Bigger plans. More governance. Tighter reporting. But these do not solve the central portfolio problem.
Organisations still deliver less than they should. Strategic outcomes still arrive late. Capacity is consumed without producing proportionate value, and the people running portfolios often know something is wrong even when every project on the dashboard is green.
Flow Economics exists because portfolio performance is not simply a project management problem. It is an economic one. And it needs its own discipline.
Many organisations are trapped in the belief that if individual projects are well planned, well governed and delivered successfully, the organisation will perform well. In reality, portfolio performance emerges from projects competing for shared constrained resources. When those constraints are invisible, the illusion persists, and investment in PMO maturity fails to move the needle because the thinking is anchored at the wrong level.
A framework for managing portfolios as economic systems rather than collections of projects. It connects three things that are usually managed separately.
The economic worth of outcomes, and the cost of delaying or diluting them.
How work actually moves through the portfolio, and where it slows down.
The limited resources, skills or decision points that govern the pace at which value can be delivered.
A method tells you what to do. A field changes how you think. Flow Economics does not prescribe a fixed set of ceremonies or templates; it changes the questions leaders ask, and therefore the decisions they make.
Flow Economics is not built from a single source. It draws on five connected streams of thinking.
Provides the economic language for understanding delay, investment health and project value over time. Stephen Devaux's work on DIPP, Drag and Drag Cost is central to this foundation.
Explains why portfolio performance cannot be understood by looking at projects one at a time. Albert Ponsteen's academic work shows how shared resource contention creates effects that are invisible at the individual project level.
Explains why the performance of the whole system is governed by its constraints, and why local optimisation often damages global results. Jan Willem Tromp brings this lineage directly into the Flow Economics worldview.
Makes these ideas usable in real organisations. Oleksii Mikhalevich's work on drag calculation, capacity intervention and algorithmic portfolio analysis helps turn the theory into something that can be operationalised.
Reinforces and extends the worldview. Mike Hannan's Fruitful Project Management work, and his contribution as a co-author of PMBOK 8, bring the language of investment, throughput and portfolio economics further into mainstream project management.
A Project Management Office asks whether projects are on track. A Value Management Office is accountable for value delivery across the portfolio: investing in the right work, allocating constrained capacity to the highest-value uses, and intervening where economic loss is accumulating.
The first two modules of the Flow Economics course are free and introduce the foundations through practical examples.
Start the free moduleSix levels of organisational maturity, from purely activity-focused delivery to constraint-aware value optimisation. Most organisations sit between levels two and three; the shift from three to four is where the thinking begins to deliver compounding returns.
Keep everyone busy. Success is measured by utilisation, prioritisation is informal, and chronic overload is normal.
Individual projects are delivered well, but the portfolio is still a collection of independent efforts competing unseen for the same resources.
Portfolio governance and dashboards exist, but prioritisation is still human-led and political.
Constraints and Theory-of-Constraints language enter the conversation, understood intellectually but not yet operationalised.
The constraint drives priorities, and reprioritisation is guided by the system rather than by intuition.
Work is sequenced to maximise the economic value produced per constrained hour. Value, flow and economics act as one decision system.
Organisations are running out of road on traditional PMO maturity. Governance has been tightened and agile adopted at scale, yet the underlying problem, too much work pushed through too few constrained resources, remains untouched.
PMBOK 8 has formally reframed projects as investments, making economic thinking at the portfolio level increasingly difficult to avoid. And the tools, portfolio simulators and shared resource platforms, are now mature enough to support real decisions rather than just analysis.
Where does your portfolio actually sit? The six-level model for scheduling as economics, and the path up.
Explore the framework →Why an on-time, on-budget project can still destroy value, and what a portfolio is really optimising for.
Explore the framework →The distance between strategy and delivery, named as an economics problem rather than a discipline problem.
Explore the framework →The hidden price of delay: what a slipping project actually costs the portfolio, in money, per day.
Explore the framework →The forward-looking measure of whether a project is still worth finishing: value remaining versus cost to complete.
Explore the framework →The single number that ranks work by what it returns on your scarcest resource, the constraint.
Explore the framework →Why adding more projects past a point reduces throughput: the capacity paradox in one idea.
Explore the framework →The first two modules of the course are free, or read the latest thinking as it is published.
Start the free course Read the insights