It goes without saying that @oneknightinprod is the best product podcast out there. I don't listen to other product podcasts & neither should you. All other product podcasters are my enemy! I would never give them any publicity. Apropos that, here's some you should not listen to:
"PM & Leadership guidance, straight to your ears."
"Product Thinking" with @lissijean, with a mix of product thinkers and "Ask Melissa" sessions
"Lenny Rachitsky interviews world-class product leaders and growth experts to uncover concrete, actionable, and tactical advice to help you build, launch, and grow your own product. "
"Lenny's podcast" with @lennysan and a bunch of product thinkers
Ah professional services. The typical #prodmgmt rejoinder whenever anyone mentions a specific client request. How dare anyone request things! None of us really want to go down this route, but what about when we have to?
🧵
It's no secret why we don't want this. Specific client requests are rarely validated, over-specific, create tech and product debt, and can make products into a messy pile of features. And above all else there's the opportunity cost
However, sometimes you're going to get bullied by a client several orders of magnitude bigger than you, or get pressure from the top to accommodate such a request. There can be good & bad reasons for this, but let's just assume you need to do it. How? Some thoughts...
Let's talk about mental health in #prodmgmt because, whatever some naysayers might say, this is an incredibly tricky job. Even when it's going well it's hard! And it's very often not going well 🧵
Part of me wonders if this is down to many of the big books, you all know the ones, painting an aspirational vision of what product management is & what a product company should be. And, don't get me wrong, I *want* to work for one of those places. But they are few & far between
And, let's face it, even working for companies like that is hard. None of them say product management is easy! So, let's be clear, even in idealistically run, by the book companies, your average product manager's life is going to be incredibly difficult
Combining two mentoring sessions that had similar themes - that tricky situation where the engineering team and product team are misaligned, and this is affecting the progress of the product & dissatisfying customers
So in this age of empowerment & product trios we should call out the key responsibilities of the 2 teams, broadly:
• Product team owns the why & the when, based on market & customer understanding
• Dev teams owns the what & the how, what's possible and the effort involved
The "what" is more of a shared responsibility between dev & UX & product, but the key here is that we want devs to work with us collaboratively to define a solution that is technically feasible, business viable, customer usable (and ethically defensible)
From today's mentoring, talking about the need from leadership to constantly race forward and building new stuff (for competitive advantage / keep sales happy / make clients excited etc). It's a common problem that I've come to refer to as the Barbarossa problem
Operation Barbarossa was Hitler's attempt to overtake Russia by reaching Moscow at lightning speed. It was risky but had high rewards. It also failed spectacularly, as we all now know. The reasons were many, but I'll cherry pick the ones that make my point
A big part of the problem with Barbarossa was that Hitler's army moved faster than their supply lines could keep up. This meant that their troops were isolated and eventually cut off. They got within sight of Moscow but ultimately got bogged down and ultimately repelled.