We scan new podcasts and send you the top 5 insights daily.
Job titles like "Product Manager" are less important than ensuring key accountabilities are met. A successful product engine needs someone who prioritizes outcomes, someone who investigates the problem space, and someone who prevents cross-team collisions. Assign these roles regardless of titles.
Creating roles like "AI PM" or "database PM" is what author Marty Kagan calls "product theater." It gives the appearance of specialization but often creates artificial silos, fragments the product organization, and hinders holistic product thinking. Real competency comes from skills, not labels.
The most critical role on a team is the "product visionary"—the person with a clear, customer-backed vision. This person can be an engineer, a designer, or a PM. Great leadership involves identifying and empowering this individual, no matter their function, rather than assuming it's the PM's job.
Product managers don't code, design, or conduct research. Their unique value is providing clarity through strategy, requirements, or a North Star vision. This clarity empowers the entire team to execute their specialized roles effectively and succeed.
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.
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.
The 'CEO of the product' metaphor is misleading because product managers lack direct authority. A better analogy is 'the glue.' The PM's role is to connect different functions—engineering, sales, marketing—with strategy, data, and user problems to ensure the team works cohesively towards a shared goal.
On the Codex team, the PM role is not seen as a traditional leadership position. Instead, it's a support function focused on doing whatever is necessary—bridging gaps, coordinating, and sometimes criticizing—to help the team succeed, rather than directing strategy from the top.
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.
Optimal product leadership structures separate the long-term, visionary role from the tactical, execution role. One person focuses on the big picture and selling the future ("the house"), while the other translates that chaos into immediate, actionable work ("fixing the walls").
Frame the product manager not as a feature owner, but as the central communication hub. Their primary function is to connect business, stakeholders, engineering, and design, navigating complex relationships and translating needs across disparate groups.