I want to talk about something I genuinely love.
Not in the "this is a good professional framework" way. In the "I think about this on holiday" way. In the "I will corner you at a conference and talk about it until you either agree with me or flee" way.
Lean Product Management.
Now, if you've been following along on this blog, you'll know we've spent some time in Scrum territory — sprints, user stories, definitions of done, the occasional flying monkey. And Scrum is useful. It really is. But Lean? Lean feels alive to me in a way that Scrum sometimes doesn't. And I want to try and explain why.
🏊 The Swimming Pool vs. The River
Here's how I think about the difference.
Scrum is a swimming pool. It's structured, predictable, and safe. There are lanes. You know the distance. You know exactly when you'll turn around. Every two weeks, you touch the wall, you catch your breath, and you go again. For a lot of teams and a lot of contexts, that's exactly what you need.
But nothing wild lives in a swimming pool.
Lean is a river 🌊. It's always moving. It shapes itself around the landscape — around real obstacles, real constraints, real feedback from real users. It doesn't stop and restart on a fixed schedule. It just keeps flowing, finding the most efficient path, clearing blockages as it goes.
And things live in rivers. Ecosystems form. Stuff actually happens.
That's what Lean feels like to me as a way of working.
♾️ Continuous, Not Cyclical
The thing that changes everything about Lean is that it's continuous.
In Scrum, value is delivered in cycles. A sprint ends, a sprint begins. There's ceremony around the transition — planning, review, retrospective. All useful things! But the rhythm is fixed, and sometimes reality doesn't match the rhythm. Sometimes the most important thing to work on becomes clear on day eight of a two-week sprint. Sometimes a user tells you something on a Tuesday that should change what you're doing by Wednesday.
Lean says: fine. Change it.
There's no waiting for the sprint to end. No "let's add it to the backlog and pick it up next time." If something is the most valuable thing to work on right now, you work on it right now. The flow is continuous and the priorities respond to what's actually happening — not to what you planned three weeks ago.
This isn't chaos. Lean is not "make it up as you go along." It's something much more disciplined than that. It's a commitment to always doing the most valuable thing, with as little waste as possible, and with the full capacity of your team focused on moving work through to completion rather than starting lots of things and finishing few of them.
🗑️ The Beautiful Obsession with Waste
Lean has a word for anything that doesn't add value: muda. Waste.
Unnecessary meetings? Muda. Work that nobody asked for? Muda. Features that took three weeks to build and have never been used? Very expensive muda. Waiting. Handoffs. Rework. All muda, muda, muda. It is so fun to say, try it!
And I find this genuinely liberating. Because Lean gives you permission — no, it gives you a responsibility — to ask "why are we doing this?" about everything. Not destructively. Curiously. With the genuine intention of protecting the team's time and the user's experience from things that don't serve either.
In practice this means: smaller batches of work, completed fully before moving on. Limits on how much is in progress at any one time (because half-done work is worth nothing). A constant eye on where things are getting stuck and why.
It means your team spends more time finishing things and less time juggling things.
💚 Why I Love It
Here's the honest answer: Lean trusts me.
It trusts me to use my judgement about what the most valuable thing to work on is, rather than binding me to a plan made two weeks ago. It trusts the team to know when something is done, rather than waiting for the ceremony of a sprint review to say so. It trusts that the people closest to the work have the best view of what's blocking it.
That freedom — that flexibility to respond to reality as it actually is, rather than as you predicted it would be — is where I do my best work. It's where I've seen teams do their best work too.
Scrum is a great place to learn the shape of product thinking. The vocabulary, the cadence, the discipline of breaking things down. But Lean is where I feel like a product manager rather than a process manager.
It's the river, not the swimming pool. It's always moving. And I genuinely love it 🌊.
Until next time, my product fiends 💀.
