AI Native Product Cadence

Sources#

• Anthropic's Boris Cherny: Why Coding Is Solved, and What Comes Next
• How Anthropic's product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code)

Summary#

Cat Wu's account of how Anthropic ships at a pace that surprises observers. Cycle time per product feature went from 6 months → 1 month → sometimes 1 day. The mechanisms are mostly removed process, not added: research-preview branding to lower commitment, mission-as-tiebreaker to remove cross-team negotiation, evergreen launch room with same-day docs/marketing turnaround, no PRDs for ambiguous features, and engineer-with-product-taste as the unit of delivery (see Engineer PM Convergence).

What "fast" actually looks like#

• A team-member's idea on Monday → research preview live by end of week.
• Source: Lenny: "Someone made a calendar of launches across Anthropic, and it was literally every day a major feature or product."
• "Sometimes" 1-day timelines for individual features, not the bulk — but the bulk is one-month, where industry norm is one-quarter.

What does not explain it#

Cat is asked directly whether internal access to Mythos explains the velocity:

"It's not fully Mythos. We do use the models internally, and I think this has increased our rate of shipping a little bit, but I don't think it explains the bulk of the increase. I think a lot of it is the process and the expectation on the team."

Take seriously: the model isn't the bottleneck; process is.

Six practices that compose the cadence#

1. Research-preview branding#

Most launches ship as "research preview" with explicit branding. This:

• Sets user expectation that the feature is early and may change
• Lowers internal commitment — team isn't locked into supporting it forever
• Allows ship-without-completeness — get the idea in front of users in a week, iterate based on feedback

2. Mission as tiebreaker#

"If there's two competing priorities, we'll talk about which one is more important for Anthropic's mission."

Removes the most expensive coordination cost: priority debates between teams. The mission ("safe AGI for humanity") sits above any individual product. When teams conflict, the mission decides — and "everyone will stand behind the one we decide."

This is process-removal via shared values rather than process-addition via meetings.

3. Evergreen launch room#

"Engineers post [a finished feature] in our evergreen launch room. Sarah who leads our docs and Alex who leads PMM and Tar and Lydia on Devril just jump in and can turn around the marketing announcement the very next day."

A standing channel where finished features get docs + marketing same-day. This eliminates the sequential handoff (engineering → PM → marketing → docs → ship) that costs most teams weeks.

4. PRDs only when needed#

• Ambiguous features → 1-pager: goals, delightful use cases, current failure modes
• Heavy-infra features → full PRD
• Most features → no PRD; metrics readouts + team principles do the alignment work

Cat's team principles list "who our key users are, why those are our key users… so that everybody on the team feels like they understand how our business works and what we're willing to trade off."

5. Metrics readouts every week#

The whole team reviews business metrics weekly. This pushes context out so individual decisions don't need PM approval — anyone on the team has the same view of what's working.

6. Engineer with product taste as delivery unit#

"Many engineers on our team are fully able to end-to-end go from see user feedback on Twitter through to ship a product at the end of the week with almost no product involvement."

When the engineer has taste, the handoffs disappear. The PM role becomes a force-multiplier (cross-functional unblocking, team principles, harder strategic calls) rather than a sequential gate.

See Engineer PM Convergence for the cross-disciplinary version.

What gets sacrificed#

Cat names the explicit trade-off:

"We're sacrificing product consistency. Historically, when code was expensive to write, you would carefully plan everything in your product suite, how every product relates to each other. Now with AI moving so quickly, we do sometimes have features that overlap with each other."

Symptoms:

• New users don't know which feature solves their problem (multiple do, slightly differently)
• Users feel "they're on this ever increasingly fast treadmill"
• Need for built-in onboarding (/powerup command in Claude Code launched late, against the original "the product should be intuitive" principle, because feature count outran intuition)

Cat's characterization: "the cost of launching a lot of features." A real cost, not a non-issue.

What gets harder#

• Code review. When agents ship more code, humans review more. Matt Pocock's confession applies: "I don't honestly know what the answer is yet."
• Quality bar. Some shipped features are buggier than Cat would like. Acceptable because "as long as it's not blocking the core use case, it's okay because we'll hear the feedback and we'll fix in the next release."
• Career ladders / role clarity. Implicit casualty of Engineer PM Convergence.

Cultural substrate: face challenges with a smile#

"Our team is full of people who lean into the chaos. We try to face every challenge with a smile because there's always so much going on. There's always so many risks and tricky situations that if you get too stressed about anything you'll burn out."

Hire industry veterans who know how to maintain energy across long ramps; bias for low-ego people who treat the chaos as exciting rather than overwhelming. Lenny's observation: every Anthropic employee he's met is "chill and optimistic."

"Just do things"#

Cat's life motto. Captures the substrate that makes the cadence possible: people don't wait for permission, jobs aren't "fake" but role boundaries are flexible, action is the default. When this collides with mission alignment, you get Anthropic's velocity. Without mission alignment, "just do things" produces drift.

Connections#

• Cat Wu — primary articulator
• Boris Cherny — converging report ("we plan in 1 week out")
• Engineer PM Convergence — the role architecture that makes the cadence work
• Harness Shrinkage as Models Improve — internal harness pruning is itself an example of the cadence applied to internal tooling
• Claude Character as Product — character work moves at this same cadence; Amanda's iteration loop is a tight example
• Claude Code Best Practices — the public artifacts of a team operating at this cadence
• Human-AI Accountability Redesign — the cross-functional/workforce mirror of internal cadence redesign; HBR's prescription generalizes Anthropic's approach
• AI Employee Framing — pushback on "anthropomorphizing accelerates adoption"; per HBR, what actually accelerates is managerial role-modeling — consistent with Cat's "everyone codes" practice

Open questions#

• Does the cadence scale beyond ~100 people? Anthropic itself is bigger (~30-40 PMs alone), but the Claude Code team that visibly drives cadence is small.
• What's the equivalent of research-preview branding for B2B enterprise launches where customers expect stability? Cat doesn't address.
• How much of the cadence is structural (process choices) vs cultural (talent density)? Probably both, ratio unclear.

Derived#

• Learning to Co-Work with AI: A Software Engineer's Field Guide — taste-calibration loop and lunchtime vibe-checks adopted as individual practices

Sources#

• How Anthropic's product team moves faster than anyone else | Cat Wu (Head of Product, Claude Code)
• Anthropic's Boris Cherny: Why Coding Is Solved, and What Comes Next