7 Counterintuitive Product Lessons from Anthropic's Head of Product

Vora starts with who a product is for and what they need to do. People are stretched and usually do not want to learn another tool, so teams should weigh the cost of extra features against the cost of leaving them out. At WhatsApp, the goal was to make messaging work for anyone; the core experience still needs improvement before a product earns the right to add more.

Vora asks whether a proposal makes clear who it serves and what it helps them do. Simplicity is not always the right choice: Facebook ads customers wanted powerful tools, so the team needed to explain its trade-offs clearly. She also recommends giving senior leaders a reasoned recommendation, not just a summary of gathered information.

Vora says a strong strategy with weak execution leaves teams unsure whether the plan or its delivery failed. A workable strategy paired with strong execution creates frequent chances to ship, learn, and adjust. She favors a minimum viable strategy that names the customer, what to build, why the team might win, and the key risks.

Teams can agree in advance which decisions need approval and set limits for changes they can roll back if they cause problems. Vora suggests office hours or quick decisions in Slack when reviews otherwise take weeks. She also recommends spending time with customer feedback each week and questioning internal work that slows delivery without helping customers.

Vora advises choosing a weekly priority, blocking time for it, and explaining that focus when declining meetings. She expects product managers to work across boundaries: test an idea, do basic market analysis, sketch a go-to-market plan, and use available tools to move it forward. In a changing field, she values first-principles thinking and willingness to learn over relying on a copied playbook.