Even with AI accelerating development, a PM's core role is managing what *isn't* being built. The ability to calculate Total Cost of Ownership (TCO) and strategically say "no" is more critical than ever, as even quickly-built features have long-term costs that displace other opportunities.

The core job of a Product Manager is not writing specs or talking to press; it's a leadership role. Success means getting a product to market that wins. This requires influencing engineering, marketing, and sales without any formal authority, making it the ultimate training ground for real leadership.

A product manager's primary role is not just managing roadmaps but injecting courage into the team. This means making unpopular decisions, like scrapping a project after months of work, to ensure the team is always building the right thing, even when it's difficult or requires challenging leadership.

The PM role is intentionally undefined, meant to adapt to a team's needs—from strategy to quality control. However, these functions can often be filled by a strong engineering lead or designer, making dedicated PMs non-essential, and potentially harmful, on smaller teams.

While engineers focus on what's feasible, a PM's job is to be the dreamer, pushing for the ideal user experience even when told it's too hard. This 'unreasonable' conviction forces the team to find creative solutions and prevents settling for mediocrity.

In an organization still running in project mode, the 'Product Manager' title is misleading. The role is often relegated to organizing work and scheduling tasks for engineering. A true product model requires empowering these roles with the mandate, skills, and market access to make strategic decisions.

As leaders face pressure to justify investments, PMs must be able to calculate and articulate the business return on their team's cost. This involves a back-of-the-envelope understanding of team salaries and development expenses versus the financial impact of their work.

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.

Ben Horowitz argues that many product managers get lost in activities like writing requirements and pitching customers. While these tasks are work, they are not the job itself. The one and only measure of a PM's success is delivering the right product at the right time. All other efforts are secondary and meaningless if this core objective isn't met.