Cat Wu runs product for Claude Code at Anthropic. Her team ships features in a day. Not a sprint. Not a week. A day. And she just told Lenny Rachitsky something that should rewire how every operator thinks about building right now: the cost of writing code has collapsed, and the skill that matters is deciding what to write.
That is the entire shift. Everything else is a consequence of it.
For two decades, product management was a coordination job. You wrote PRDs, aligned partner teams, negotiated quarterly roadmaps, and shipped a feature every month or so. The work was slow because code was expensive. Teams needed four months to build a thing, so a PM spent four months making sure the thing was worth building.
That calculus has inverted. When a feature can be stood up in a day, the bottleneck is no longer engineering capacity. It is taste. It is knowing which of ten thousand GitHub issues is worth touching. It is knowing whether the current model can actually pull off the feature you are imagining, or whether you are shipping a broken promise.
Wu's own team operates on a rule worth stealing: ship almost everything as a research preview. Brand it clearly as an early idea. Tell users it might not survive. This one framing move reduces the commitment to a feature from "we shipped it, we own it forever" to "here is a draft, tell us what works." Commitment becomes cheap. Feedback becomes the roadmap.
If you are running an agency or a D2C brand or a tech platform, steal this verbatim. Half the reason your team ships slowly is because every release is treated as a marriage. It isn't. It is a first date.
The second thing worth sitting with: Wu openly says the PM role and the engineer role are merging, and Anthropic is hiring engineers with product taste over PMs who cannot ship. Designers on Claude Code write frontend code. Engineers take an idea from Twitter and turn it into a working feature by lunch. The PM job survives only as a multiplier role for people who can already build. The pure-coordinator PM is a dying species. Operators who cannot at least drive a coding agent are about to be priced out of their own product.
The third lesson is the one that hits the hardest, and it is buried under all the talk of velocity. Wu calls it the last-mile rule. Building 95% of a feature is the easy part. Pushing it from 95% to 100% — where it actually works for users every time, not just in the demo — is the entire job. Most teams ship half-baked features because the model fails five percent of the time, and now you have a broken process that you half-trust, which is worse than no process at all. Either put in the elbow grease to push it to 100%, or do not build it. The middle ground is the worst place to be.
Watch Amazon sellers and D2C operators doing this weekly. They build a half-working repricer, a half-working ad bidder, a half-working review responder, and then spend more time babysitting the automation than they saved. Wu's point is simple: the last mile is the entire job. Skip it and you have bought yourself technical debt dressed up as productivity.
There is a deeper layer under all of this, which is how Anthropic itself moves. Wu said that if Claude Code failed but Anthropic succeeded, she would be happy. Teams trade off against one another openly because the mission sits above any product line. That clarity is why the company ships a feature a day across a dozen surfaces without tripping over itself. It also explains some decisions that looked weird from outside — like sunsetting features built for old models because the new model makes them unnecessary. You don't carry around scaffolding that was put up to compensate for a previous model's weakness; you assume the next model will close that gap and you build with that future capability to catch up. Code review was exactly this — attempted for two years, only launched when Sonnet 4.6 could actually catch bugs.
If you are building for today's model only, you will be blindsided every quarter when a new model changes what is possible. Build for six months from now. The model will eat your harness for breakfast, and the things you scaffolded around to compensate for its weaknesses will quietly become unnecessary. That is the point. Remove the crutches. Keep the scaffolding honest.
The one-line takeaway: stop coordinating, start shipping. Stop prototyping, start using. Stop pretending 95% is done.
The bar moved. Your roadmap should too.
Source: Cat Wu on Lenny's Podcast
No comments:
Post a Comment