Why do you need Portfolio Management? Just Create Product Teams...


"Instead of Portfolio Management - Just Create Product Teams" - Have you heard that before, Reader?

While I understand the angst against Portfolio Management Theater as a solution to Agile Theater...

And while I agree wholeheartedly that the north star is to descale by reorganizing around value

I find reality a bit more nuanced....

Most leaders I encounter can't "just create product teams" their way out of decades of complex products and systems.

None of them are Jeff Bezos - they don't have the mandate or budget to move all the way to an environment where all strategic goals can be achieved solely by empowered product teams working on their own.

Yes, AI can help some by helping smaller teams tackle a wider breadth of the codebase. They can help by reducing tech debt (or improving automation coverage to make it safer to change things).

Yes, through proactive investment into platforms and enabling teams, we could minimize the need for managing cross-initiatives.

However, in most cases, at best, we will flip the product organization to rely much more on empowered teams and reduce the percentage of portfolio-level concerns.

We won't be able to fully flatten the product organization anytime soon.

So it might not be popular with the cool agilist crowd, but I do think Lean Portfolio Management has a role.

It has a role in bringing agile and product operating systems to tackling these strategic cross initiatives.

In providing intent, context, and guardrails that ENABLE and guide these empowered product teams.

It provides the surface area for leaders to learn, apply, and lead by example using product, evidence-informed, agile thinking...

And what I'm most excited about these days is how it helps bring agile and product thinking to the broader organization, even beyond the boundaries of the technology/product investments.

Scaling w/ Agility

Are You Struggling to Scale Your Organization ? Need agility but dubious of process BS/dogma? I share reflective, pragmatic, principled takes on how to approach scaling your organization leveraging the essence (rather than theater) of product operating models, agile practices and frameworks, and business operating systems such as EOS and OKRs.

Read more from Scaling w/ Agility

Product development concepts come in handy every time you're developing something. Whether that thing is software, product, or even a point of view. The first sentence in this email is a point of view (POV). I want this point of view to be effective - I want people to understand what I mean, be intrigued by it, take action, and hopefully see me as a thought leader / expert in this space that they'll want to follow / listen to more. It took me a while to develop this point of view. To carve a...

Context is King You’ve probably encountered this term in the context of AI. You won’t get far with AI, even with amazing prompting techniques, if AI doesn’t have the right context. Many people focus on the Data aspect of context – what’s in our CRM, in our collaboration tools, in our ERP, in any of our vertical systems. Another interesting aspect is the intent – what are we trying to achieve? What is our strategy? What problems are we focused on? Who are the players? Some of that information...

Hey Reader, Before you fix teams, fix the system they operate in. Most organizations focus their improvement efforts at the team, program, or product level while maintaining the same organizational operating system—how they make decisions, fund work, and measure success. These teams might be using the latest and greatest processes (Agile, Product Model, Lean Startup, take your pick) but they still need to manage countless dependencies. The funding and GTM processes are still following classic...