Embarking on Your Product-Oriented Lean Portfolio Management Journey

Are you at the stage where traditional portfolio-level processes and behaviors present the most significant impediment to agility?

I see this often. The organization spends six or seven-figure amounts on an agile transformation. 

Teams and Teams of Teams are working in Agile/Scrum/SAFe. 

Still, the promised land of outsized value creation and improvement of time to market (rather than flow time of stories or “features”) is elusive. 

Looking at the conversations around budget, governance, and driving your significant business initiatives, agility is the last term that comes to mind (bureaucracy and large ship struggling to maneuver are more apt descriptions)

You envision finding an organizational operating system that orients around outcomes, where the right people collaborate closely with each other, where people naturally and easily integrate and experiment, and where there’s a goldilocks mix of alignment, autonomy, and guardrails.

You decide it’s time to bring agility and product-orientation to the portfolio level.

What does that look like?

Let’s discuss transforming your IT portfolio from a feature factory managing scattered investments to creating a product-oriented mega-lab that drives growth, value, and resilience.

You can think about the journey to a product-oriented portfolio in four stages: Crawl, Walk, Run, and Fly.

Each stage helps your organization evolve towards agility, evidence-based decision-making, and continuous alignment.

Crawl: You start by recognizing that you already have a portfolio of investments, even if it’s not formalized. In this stage, you start to understand your portfolio and the flow (or lack thereof) of your significant investments.

Walk: Begin actively managing the flow and shaping demand. (Saying No, or not yet) It’s about turning a collection of projects into cohesive products—creating an intentional balance between technology and business investments. Starting to have conversations around which decisions to manage at the portfolio level, and which to empower product teams to have. 

Run: Now, it’s about aligned autonomy. Teams are free to innovate, while strategic goals keep everyone focused on the outcomes that really matter. Stable funding decoupled from product cycles helps teams thrive without constant budget concerns.

Fly: Finally, you’re in full agility mode—treating your entire business like a product. Lean Startup principles guide how you adapt and grow, and every aspect of the industry evolves in response to real-world feedback. 

This journey isn’t about frameworks or processes—it’s about behaviors.

In the early stages, it is focused on establishing flow. Then, it is about reorganizing around value and outcomes and eventually being evidence-informed. 

Where are you in this journey? Which behaviors are you seeing? What are the next ones to focus on? 

PS What if there was a way to navigate the portfolio agility journey, without falling into the trap of a prescriptive itinerary that so often ends up at the (agile) theater? That would be nice, right?
If this is your challenge, see Portfolio Agility and contact me for a clarity conversation.