With code becoming cheaper and faster to write thanks to AI, the critical differentiator is no longer the ability to build, but the judgment and taste to decide what is worth building among countless user requests and possibilities.
With priorities shifting from "P0" to "P000" in a single day, the key hiring trait is psychological resilience and a positive attitude towards chaos. The ability to embrace challenges and brutally prioritize is essential to avoid burnout on high-velocity teams.
The key skill for an AI PM is knowing a model's current capabilities. This is built by intensely using the model and, crucially, asking it to introspect on its own unexpected behaviors to understand *why* it made a mistake, revealing gaps to fix.
Users often abandon AI automations at 95% accuracy because they still require manual oversight. The real value is unlocked only by investing the final effort to teach the AI and refine the process to achieve 100% reliability, truly offloading the task.
With AI accelerating development from months to days, PMs must focus on unblocking engineers and launching weekly. This supersedes traditional emphasis on long-term, cross-team roadmap alignment, which was crucial when code was more expensive to produce.
Anthropic prototypes features like code review even when model accuracy is too low for a public launch. This allows them to identify what's missing and be ready to immediately swap in a new, more capable model to close the gap and launch ahead of competitors.
A core reason for Anthropic's speed is its mission-driven culture. Teams willingly de-prioritize their own goals and KRs to serve the overarching company mission, enabling fast, unified execution on major priorities without internal politics.
Many early AI product features, like Claude Code's initial "to-do list," are crutches built to compensate for model weaknesses. As underlying models become more capable, they perform these functions naturally, allowing teams to remove the crutch features and simplify the product.
Instead of hiring more PMs to manage faster engineering cycles, Anthropic focuses on hiring engineers with strong product taste who can ship end-to-end. This reduces overhead and blurs traditional roles, as most PMs and designers also have engineering backgrounds.
Anthropic has seen a proliferation of personalized work apps created by employees in roles like sales. Tools like Claude Code lower the barrier to building software, allowing teams to create tailored solutions for repetitive tasks instead of using generic tools.
To ship features weekly, Anthropic PMs use a repeatable framework: 1) Set clear user goals to reduce ambiguity, 2) Brand launches as "research previews" to lower shipping commitment, and 3) Create tight, low-friction processes between engineering, marketing, and docs.
Unlike traditional software development, where consistency is paramount, AI development requires testing many ideas quickly. Anthropic intentionally launches overlapping features to see which form factor users prefer, accepting the cost of a less consistent UX in exchange for speed and market feedback.
The Head of Product for Claude Code defines her role as creating the pragmatic path to the tech lead's long-term "AGI-pilled" vision. She focuses on cross-functional execution to clear the shipping path, creating a powerful visionary/executor leadership dynamic.