Written by Pétercsák Réka, PSM, PSPO, PCC, SPC
Why Portfolio Management Doesn’t Work Well in Most Organisations
In most organisations, portfolio management doesn’t fail because people lack skills or because the right tools are missing. Much more often, the problem lies in the system itself: it is designed to optimise projects—not the flow of value.
The Limits of Project Thinking in an Uncertain Environment
At first glance, this may not seem like a significant difference, but in practice it is. Traditional project logic assumes that we can define in advance what should be done, at what cost, and with what outcome. In a stable, predictable environment, this approach can work. In a fast-changing and uncertain world, however, it increasingly leads to slow decision-making, overloaded portfolios, and disappointing business results.
The Shift in Mindset: Portfolio as a Strategic Decision System
In recent years, this has led to a gradual yet clear shift in mindset. The portfolio is no longer seen as simply a “list of projects to manage,” but as a strategic decision system that continuously realigns initiatives and directs capacity toward the highest business impact.
There are several clear signals of this shift. More and more organisations are moving away from annual planning toward continuous portfolio rebalancing. The focus is shifting from projects to products and value streams. Emphasis is moving from delivered output to achieved business outcomes. Real-time portfolio visibility is emerging, and focus is becoming more intentional: fewer initiatives, but greater impact.
In the following sections, we outline key principles and organisational practices that can support a more effective transition toward agile portfolio planning.
The principles of agile portfolio management and their structure
Agile (adaptive) portfolio management is not a specific methodology or framework. Rather, it is a way of thinking that helps organisations make better decisions about what to start, when to start it, and how to execute.
These principles do not emerge “out of thin air.” They are rooted in Lean and Agile thinking; for example, Kenneth S. Rubin explores related concepts in his book Scrum Essentials, examining how economically sound, system-level decisions can be applied at the portfolio level.
One of the key strengths of these principles is that they do not appear as isolated rules. Instead, they form a coherent system that spans the entire lifecycle of initiatives: how ideas enter the portfolio, how they are prioritised and initiated, and how they progress through delivery.
Based on this, the principles can be grouped into four main categories:
1. Inflow – how ideas and opportunities entering the portfolio are filtered and managed
2. Sequencing – how priorities are set based on economic, business, and organisational considerations
3. In-process - how ongoing initiatives are managed, and how flow is optimised
4. Outflow – when and how new initiatives are started based on available capacity
This structure helps shift the focus away from individual tools or techniques and toward understanding the portfolio as a complete system.
Key Operating Principles in Practice
1. Managing Incoming Work – Inflow
When managing incoming initiatives, a well-defined economic filter—tailored to the organisation’s context—plays a critical role. A well-functioning portfolio does not attempt to analyse everything in detail. Instead, it quickly filters for opportunities that create disproportionate value relative to their cost, and lets go of the rest. This is especially important in large organisations, where the number of “good ideas” is virtually unlimited.
Another common pitfall is thinking in overly large batches. When many initiatives are analysed and prioritised at once—such as during an annual planning cycle—it consumes significant time and energy. Moreover, a portion of these initiatives will never be started, or by the time they are, the underlying assumptions may already be outdated. It is therefore far more effective to process incoming work continuously, in smaller batches.
At the same time, the portfolio must remain open to emerging opportunities. The environment is constantly changing: new technologies appear, market conditions shift, and unexpected events occur. If the portfolio is too rigid, it cannot respond in time. An agile portfolio, by contrast, is able to recognise and incorporate such opportunities quickly.
From a value realisation perspective, thinking in smaller, incremental releases is essential. Instead of delivering everything at the end of a large project, it is more effective to move step by step, reassessing after each increment whether it still makes sense to continue. This reduces risk and enables earlier value realisation.
2. Prioritisation and Decision-Making – Sequencing
One of the most important principles is that we optimise not for the success of individual projects, but for the performance of the portfolio as a whole. This means that a given initiative may be promising on its own, yet still be deprioritised if it does not deliver the greatest value at the portfolio level. For many leaders, this is counterintuitive, as decisions are made at a system level rather than locally.
Closely related to this is the concept of Cost of Delay. When we prioritise items in the portfolio backlog, we are making economic decisions. What we choose not to start now will be delayed—and will also deliver value later. This lost or delayed value can often be quantified. For example, if a new product reaches the market three months later, it may result in three months of lost revenue or competitive advantage.
Another common pitfall is the pursuit of excessive precision. Many organisations invest significant effort in detailed cost and resource estimates, even though the future is inherently uncertain. An agile approach, in contrast, emphasises that decisions do not require perfect accuracy—only “good enough” estimates. For example, a T-shirt sizing approach (S–M–L–XL) is often sufficient to determine whether an initiative is worth pursuing.
3. Managing Work in Progress – In-process
Portfolio decisions should not be driven by resources already spent, but by expected future value. Sunk cost thinking often leads organisations to continue initiatives that no longer support strategic goals, simply because “we’ve already invested so much.” Agile portfolio management takes a different approach: decisions should be continuously revisited based on how much value an initiative is expected to generate from this point forward—and how that compares to available alternatives. This makes it possible to stop or reprioritise work in a timely manner and redirect capacity toward initiatives with the highest potential business impact.
4. Starting and Releasing Work – Outflow
At the operational level, one of the most important shifts is the focus on optimising flow. Traditional thinking often aims for 100% utilisation—ensuring that everyone is always busy. In practice, however, this leads to overload and slower delivery. An agile approach emphasises that the goal is not to keep people constantly occupied, but to ensure that work flows through the system as smoothly and quickly as possible.
This is closely linked to the use of WIP (Work in Progress) limits. When too many initiatives are started at once, all of them progress more slowly. By limiting the number of concurrent items, organisations can complete work faster—and realise value sooner.
Finally, an important principle is to start initiatives only when a full team is available. Work that begins with partial capacity often stalls, requires re-planning, and ultimately takes longer to deliver. In contrast, stable, dedicated teams enable more predictable and faster value delivery.
Lean Portfolio Management (LPM) as an Enabling Framework
These ideas are reflected in several approaches; one of the most comprehensive among them is SAFe Lean Portfolio Management (LPM), which brings together strategy, funding, and execution into a coherent operating model.
LPM structures portfolio management around three key areas:
- Strategy and investment funding – what to fund and within what constraints
- Portfolio operations – how initiatives flow through the system
- Governance – how to ensure control without micromanagement
In practice, this is realised through elements such as Portfolio Kanban, continuous prioritisation, value stream–based funding, and regular strategic and operational decision forums.
In other words, agile portfolio management principles define how we think, while Lean Portfolio Management defines how we put that thinking into practice.
Organisational Changes Enabled by LPM
One of the most significant shifts in this model is the move from project-based structures to organising around value streams. Instead of forming temporary teams for each new initiative, organisations establish stable, long-lived teams that continuously deliver value within a given value stream. This logic is reflected in constructs such as Agile Release Trains, which coordinate the work of multiple teams.
This shift is closely linked to changes in the funding model. Rather than funding individual projects, organisations increasingly adopt value stream–based funding. In this approach, a value stream receives a budget envelope within which teams can make flexible decisions about how to allocate resources.
Decision-making also evolves. Instead of relying on annual planning cycles, organisations move toward continuous alignment through regular portfolio-level events. These may include strategic portfolio reviews, where leaders reassess priorities, or portfolio sync meetings, where current status and progress are reviewed.
Control does not disappear—but it takes a different form. Instead of traditional phase-gate approvals, organisations establish clear financial and strategic guardrails. These define the boundaries, while day-to-day decisions are decentralised and made at the team level. This allows the organisation to remain both fast and controlled.
At the core of this way of working is continuous learning. Instead of detailed upfront planning, a hypothesis-driven approach emerges: progressing in small steps, validating quickly, and making decisions based on real feedback.
First Steps in the Transformation
For many organisations, the biggest challenge is not understanding what needs to be done, but where to start.
The good news is that not everything needs to change at once. The first steps can be surprisingly simple.
A practical starting point is to visualise the current portfolio flow using a simple Kanban: where ideas come from, how decisions are made, and where work gets stuck. Even this single step can lead to valuable insights.
From there, it is worth introducing regular, structured decision-making forums—not more meetings, but real decision points where strategy, execution, and funding are aligned.
And perhaps most importantly: establish shared principles. Ultimately, it is not tools or frameworks that define how an organisation operates, but the principles that guide its decisions.
Conclusion
Agile portfolio management is not just another methodology to be “implemented.”
It is a response to a more fundamental question: how can we make better decisions in an uncertain and rapidly changing environment?
Do you have any questions? Get in touch with us.
If you feel you need support with agility or agile portfolio management, feel free to reach out. You can request a free consultation, explore our agile training programs, or assess your organisation’s or team’s agile maturity through our short, free questionnaire.
