Next Steps Towards Product Portfolio Agility
Before improving portfolio agility, you need an honest read on where you actually are. A practical assessment framework for product portfolios — covering funding, flow, autonomy, and outcome-orientation.
Do not improve the portfolio before you know what is stuck
You might already be actively managing the flow of your most significant investments. You might also have started conversations about how to descale by organizing around products. Good. Now comes the harder question: what is the next constraint in your portfolio system?
It depends. Do you need stronger outcome orientation? More aligned autonomy? Better predictability? A more sustainable pace? More empiricism before big bets receive funding? The principles of agility apply at the portfolio level too, but they do not all matter equally at the same moment.
A principle-based assessment can help leaders see where they are and have a structured conversation about where to go next. The key is not to turn the assessment into a maturity-labeling exercise. Talk about why improving a specific area matters, what business impact you expect, and how it supports the strategic change you are trying to make.
This is where the path becomes less scripted. A few examples:
- When portfolio leaders wanted to improve empiricism and reduce investment risk, we changed the workflow so discovery behavior became visible. A key decision point was whether an investment had enough confidence to move into delivery or needed more discovery first.
- When a product leader wanted to empower product teams on significant initiatives, we shaped the work around outcomes and used OKR language instead of classic PRDs and business cases.
- When an enterprise was struggling with unsustainable pace, we ran a portfolio planning exercise inspired by agile planning techniques. The involved product groups built a realistic portfolio roadmap using pull mode, rather than pretending everything could fit.
- In a large enterprise with multiple portfolios, some patterns were enterprise-wide and others were portfolio-specific. For example, a Technology Services portfolio focused on applying product thinking to enabling work and nurturing internal platforms so fewer dependencies needed to be synchronized with business-facing portfolios.
Portfolio agility is not one recipe. The useful move is to name the current friction, connect it to a business reason, and choose the next intervention deliberately.
A free email course on building an agile portfolio operating model — from recognizing your portfolio to achieving true strategic flow.
Yuval Yeret helps product and tech leaders move from agile theater to evidence-informed delivery. Work with Yuval →