Roman's Product Management Podcast

Is it a good thing when product managers are hands-on and use AI to build prototypes and generate code? Will it increase productivity and job satisfaction? Will it deliver better products faster? Or will it result in poorly designed applications full of technical debt that nobody wants and needs?

Product outcomes define the specific value a product creates—for users, customers, and the business. When applied correctly, they align stakeholders, create focus, and give development teams clear direction. But getting them right isn’t easy. Too often, product teams choose outcomes that are vague, oversized, or worse, features dressed up as goals. The result? Confusion, misalignment, and roadmaps that look strategic but fail to drive meaningful impact. In this podcast episode, I’ll address these issues and provide practical advice to help you define the right outcomes that help you achieve product success.

In this episode, I explain how you can successfully implement the product operating model—based on my experience of helping companies introduce and improve a product-led way of working over the past 15 years.

Every product has a strategy. But not all product strategies are clearly articulated, let alone communicated and understood. This can lead to confusion and misalignment: Different people have different ideas about what the actual strategy is and disagree on which features should be implemented. But it doesn’t have to be this way. In this episode, I describe a clear, five-step process that helps you build an effective strategy for an existing product and create clarity and alignment.

Product teams play a key role in solving user problems and achieving product success. But who should lead the team and manage its work? The Head of Product, the product manager, or someone else? In this episode, I explain why product teams should be self-managing. I describe the benefits this approach offers and what it takes to succeed at self-management.