Going Upstream


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 phase-gate approaches.

The feature factory might be operating more efficiently, but products often fall flat when they finally reach the market.

You'll often see Team Leads, Scrum Masters, Agile Coaches working hard at optimizing team or program-level processes, without making a real impact on revenue, growth, or customer satisfaction.

The excellent book "Upstream" shares the story of two fishermen who see children floating down the river, and for a while, they rescue them as they float by, until one of the fishermen decides to go up the river to see who's "throwing kids into the stream."

These practitioners are like those fishermen. They are often not allowed to go upstream. And in some ways it's comfortable to keep fishing kids out of the water - your work is never done... (Unless someone realizes the effort is futile...)

I should know

I spent some time fishing kids out of the water early on in my agile journey.

But at some point, I got fed up with this reality.

This is when I started to leverage techniques such as Kanban to bring flow, agility, and product orientation upstream.

Over the years, going upstream has led me towards portfolio-level interventions, refining OKRs, and developing companies as products. The further upstream you go, the more impactful small interventions become.

Give me a place to stand and with a lever I will move the whole world.” ~ Archimedes

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

"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...

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...