---
id: ins_pm-should-not-ship-at-scale
operator: Amol Avasare
operator_role: Head of Growth, Anthropic
source_url: https://www.lennysnewsletter.com/p/anthropics-1b-to-19b-growth-run
source_type: podcast
source_title: Anthropic growth, CASH, and the squeezed PM
source_date: 2026-04-05
captured_date: 2026-05-01
domain: [product, leadership]
lifecycle: [process-cadence, hiring-team-design]
maturity: applied
artifact_class: framework
score: { originality: 4, specificity: 4, evidence: 3, transferability: 4, source: 5 }
tier: B
related: [ins_squeezed-pm-thesis]
raw_ref: raw/podcasts/amol-avasare--anthropic-growth-cash--2026-04-05.md
---

# At scale, PMs should up-level the why and what; not ship more features

## Claim
With 20 engineers and 1–2 PMs, the highest-leverage PM use of time is making the "why" and "what" 5% better, not personally shipping the 21st feature. Shipping for *learning* (a prototype to communicate an idea) remains valid; shipping for output is not.

## Mechanism
Engineering output is no longer the constraint. PM time spent shipping is time not spent sharpening direction. A 5% improvement in the "why" multiplies across 20 engineers' work; a single feature ship adds to the pile and degrades the average focus. PRDs largely vanish in this model, direction lives in Slack and in the heads of senior engineers who already know the why.

## Conditions
Holds when:
- The team is large enough that 1 PM serving many engineers is the actual shape.
- Engineers are senior enough to absorb direction without a PRD.
- Direction is the limiting factor; if direction is already crisp, returns to refining it diminish.

Fails when:
- The team is small and the PM genuinely is the multiplier on shipping velocity.
- Engineers need detailed specs (junior team, regulated domain).
- The org rewards visible PM output (artifacts, PRDs, ships) and punishes "thinking time."

## Evidence
> "PRDs largely dead — 70–80% of Anthropic ships have no PRD; just Slack + good engineers."

· Amol Avasare on Lenny's Podcast, 2026-04-05

## Signals
- PM calendar shifts from feature reviews to direction-setting and stakeholder alignment.
- Engineers report clarity on why, not just what; fewer "what should I work on next" loops.
- Strategy artifacts (one-pagers, briefs) get tighter while PRD volume drops.

## Counter-evidence
Brandon Chu's "PM as writer" tradition argues the artifact is the work, writing PRDs is how PMs think. Dropping the artifact may hide quality drift. In small teams or new domains, the PM shipping is exactly the leverage point.

## Cross-references
- `ins_squeezed-pm-thesis`, the structural reason the PM role rebalances