We scan new podcasts and send you the top 5 insights daily.
Marty Cagan says if you want to spend time on front-end pull requests, go be a developer. The PM's job is making sure what engineers build achieves the needed outcome, which makes product strategy and discovery more important than ever.
Even though AI enables PMs to code, it's an inefficient use of their time. Since code creation is cheap and product strategy is the new bottleneck, PMs should focus entirely on product work, not engineering tasks.
As AI tools automate coding and prototyping, the product manager's core function is no longer detailed specification writing. Instead, their value multiplies in judging, facilitating, and making the right strategic decisions quickly. The emphasis moves from the 'how' of building to the 'what' and 'why,' making decision-making the critical skill.
Building your own product forces you to confront technical realities like database migrations and architectural trade-offs. This firsthand experience provides deep empathy for engineering challenges, which in turn builds crucial credibility and improves collaboration with development teams.
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.
The "should PMs code" debate is settled. With AI tools, PMs don't need to become engineers, but they must become literate in how software is built. Modern tools make it easy to interact with codebases like Git to get answers without waiting for an engineer.
As AI tools lower the barrier to coding, the most effective PMs will evolve to contribute small code changes directly to the product. This blurs the lines between roles, unblocks small tasks, and deepens the PM's understanding of the product's construction.
The definition of "cross-functional" is shifting from coordinating between departments to embodying multiple skills. To increase speed, modern PMs must directly perform tasks in design, user research, and even coding, rather than acting as a 'glorified cross-functional secretary.'
While it's valuable for PMs to learn to build, they shouldn't forget their primary value. Their superpower isn't writing production code, but deep product sense and user empathy. Embrace new skills, but hone your core strengths to avoid becoming a lesser engineer.
AI and low-code tools are collapsing the distance between idea and execution. The traditional PM role of managing engineering and design resources is becoming obsolete. The future belongs to product managers who can personally build, test, and iterate on products, transforming them into solo builders.
The primary value of PMs and designers coding isn't to increase feature velocity. It's to gain a deep, intuitive understanding of the material they are designing with, such as how an AI agent loop works. This mastery of the medium is more critical than direct code contributions.