Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

The question "do we need product management?" often arises from a fundamental misunderstanding of the role. When organizations use product managers like a hammer to cut a branch (ship features) instead of hammering a nail (solve the right customer problem), they are misusing the tool and will inevitably question its value.

Related Insights

Transforming a feature factory into a value-driven organization is a geometric problem. It isn't enough to convince leadership. You must also change the behaviors of engineers accustomed to tickets and stakeholders accustomed to making demands. It requires a full-stack cultural change.

In legacy companies, evangelizing product jargon like 'discovery' or 'iteration' is alienating and can seem arrogant. Product managers gain more traction by using stakeholders' own language, focusing on solving their problems, and reframing product processes as simple, tangible requests for feedback, not philosophical debates.

Product Management's core responsibility is to drive the business growth of a product by delivering profitable customer value. Technical skills and building are means to an end, not the end itself. This business focus remains constant even as tools like AI change.

PMs often feel pressure to keep engineers busy building new features. The real job is to drive deep understanding, even if it means perfecting three core features rather than adding a fourth. It's better to pause building than to create a bloated, mediocre product that does nothing well.

Jack Dorsey reframed the Product Manager role as "Product Editor." The most valuable skill is not generating new feature ideas, but exercising judgment to cut through the noise, simplify complexity, and edit the product down to the essential few things that truly drive customer outcomes.

The ultimate sign of a product manager's influence is not receiving feature ideas, but being the go-to person for complex business problems. This indicates you are viewed as a strategic partner capable of diagnosing root causes, even when a solution isn't obvious.

With tools that make building faster than ever, it's easier to fall into the "build trap" of shipping features without validating their value. This shifts the primary bottleneck from execution to strategy, making the product manager's core job of identifying the *right* problem to solve more crucial than ever.

Unvalidated product ideas often originate from executive leadership or adjacent departments. A product manager's critical role is to use disciplined stakeholder management and clear communication to maintain focus on solving validated user problems, rather than simply executing on top-down directives.

Product managers are trained to conduct discovery to understand user needs, yet they frequently fail to apply this same curiosity and process internally. They don't discover what sales, marketing, and other partners need to be successful, leading to a disconnect where they only focus on shipping features rather than enabling the entire business.

A common founder mistake is hiring a first product manager to simply prioritize and ship a backlog of ideas. Instead, PMs create the most value when given ownership of a key metric and the autonomy to drive user and business outcomes.