Six months to one month. Sometimes one week. Sometimes one day. Catherine Wu’s conversation with Lenny Rachitsky is one of the clearest pictures I've seen of where product development is heading. Engineers with sharp product taste shipping end-to-end. PMs enabling and contributing to daily releases instead of guarding multi-quarter roadmaps. That's exactly the shift Slack is built for. Anthropic runs on Slack as their work OS — bringing together their people, AI tools like Claude Code, and the workflows that let them move this fast. When your collaboration layer IS your AI layer, this is what becomes possible.
My biggest takeaways from Claude Code's Head of Product Catherine Wu: 1. Anthropic’s product development timelines have gone from six months to one month, sometimes one week, sometimes one day. Part of this acceleration is access to the latest models (i.e. Mythos). Another is shipping new products into “research preview,” making clear it's early, experimental, and might not be supported forever. Another piece is an evergreen "launch room" where engineers post ready features, and marketing turns around announcements the next day. 2. The PM role is shifting from coordinating multi-month roadmaps to enabling teams to ship daily. As Cat puts it, “There should be less emphasis on making sure you are aligning your multi-quarter roadmaps with your partner teams and more emphasis on, OK, how can we figure out the fastest way to get something out the door?” 3. The most efficient shipping unit is an engineer with great product taste. On Cat’s team, many engineers go end-to-end—from seeing user feedback on Twitter to shipping a product by the end of the week—without a PM involved. Also, almost all the PMs on the Claude Code team have either been engineers or ship code themselves, and the designers have been front-end engineers. The roles are merging, and the most valuable skill is product taste, not job title. 4. Build products that are on the edge of working. Claude Code’s code review product failed multiple times because earlier models weren’t accurate enough. But because the prototype was already built, they could swap in Opus 4.5 and 4.6 and immediately test whether the gap was closed. Teams that wait for the model to be ready will always be a cycle behind. 5. The most underrated skill for building AI products is asking the model to introspect on its own mistakes. Cat regularly asks the model why it made an unexpected decision. The model will explain that something in the system prompt was confusing, or that it delegated verification to a subagent that didn’t check its work. 6. Anthropic employees build custom internal tools instead of buying SaaS products. A sales team member built a web app that pulls from Salesforce, Gong, and call notes to auto-customize pitch decks—work that used to take 20 to 30 minutes now takes seconds. Their core stack is Claude Code, Cowork, and Slack. No Notion, no Linear, no Figma. 7. Hire people who lean into chaos and face every challenge with a smile. At Anthropic, there are weeks when a P0 on Sunday becomes a P00 by Monday and a P000 by Monday afternoon. If you get too stressed about any one thing, you’ll burn out. Their team looks for people who can look at a hard challenge and say, “Wow, that’s gonna be hard. But I’m excited to tackle it, and I’m gonna do the best that I possibly can.” Don't miss our full conversation: https://lnkd.in/geKgx8Qv
Great points, Rob Seaman! The discipline underneath is the work where human judgement thrives: knowing exactly where you are between the model you have today and the one arriving in six months, and shipping from that position. The March 31 Slack launch made that same bet. Agents doing specific work where decisions happen, not AI as a promise.