Lenny's Podcast: Product | Career | Growth
00:10:29 · Lenny Rachitsky, Cat Wu
[00:10:29] S1: I want to drill a little bit further into just how you're able to move so fast. I've never seen anything like the pace folks at Anthropic are shipping at. Someone made this calendar of launches across Anthropic, and it was literally every day there was a major feature or product. So one question people had online is you guys just launched this, not launched, but built this incredible model Mythos that is still in preview because it's so powerful, people are a little afraid of what it can do. Have you guys been using this? Is this part of the reason you've been able to move so fast? [00:11:03] S0: We've been moving pretty fast for several quarters now, so I think it's not fully Mythos. Mythos is an incredibly powerful model. 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. So we're very low on process. We want to remove every single barrier to shipping things. We want to make sure every single person on the team feels empowered to take their idea from just an idea to out in the world in less than a week, sometimes even in a day. [00:11:41] S1: Cool. Oh, man. What an advantage to have the best model and also be building product. That's so cool. [00:11:46] S0: We are very lucky to be able to work with the frontier models.
00:11:46 · Cat Wu, Lenny Rachitsky
[00:11:46] S0: We are very lucky to be able to work with the frontier models. [00:11:49] S1: Oh my God, what an awesome advantage, just build a thing and then use it and then accelerate faster. It's so interesting. There's a couple of these other side things, I want to just go on these sidequest on this conversation. There's so much happening with Anthropic, and I just am so curious to get your insight. One is a week ago or so, the whole source code of Claude Code leaked. Somebody got it out there. I think it was a mistake someone made. Is there anything you comment there, just like what happened? What went wrong? What should people know? [00:12:15] S0: So we immediately looked into this when we saw it. We realized that this was the result of human error. There was a human working with Claude to write PR. This was just an update to how we release our packages and it actually went through two layers of human review, and so this was a result of human error and we've hardened our processes to make sure that it doesn't happen in the future. [00:12:40] S1: Is this person still at Anthropic? Are they doing all right? [00:12:42] S0: Yes, yes. It's a process failure, and the most important thing is to just learn from it and to add more safeguards so that doesn't happen again, and so that's what we've been focused on and most of those have shifted.
00:12:42 · Cat Wu, Lenny Rachitsky
[00:12:42] S0: Yes, yes. It's a process failure, and the most important thing is to just learn from it and to add more safeguards so that doesn't happen again, and so that's what we've been focused on and most of those have shifted. [00:12:54] S1: Okay. Another question I had is OpenClaw. So recently there's been this move to keep people from using Claude's subscription with their OpenClaws. People got really upset. They're confused why this is happening. It feels like there's harm caused to the open source community. What do people need to understand about what went into this decision? [00:13:18] S0: So we've been seeing a lot of demand for Claude, and we've been working very hard to both scale our infrastructure and also to make our harness more token efficient so that you can get more usage out of it. It wasn't designed for third-party products, which have different usage patterns than our first-party ones. We spent a bunch of time trying to figure out what is the most seamless transition that we can offer, and so I was very happy to be able to say that everyone gets some credits alongside their subscription. But yeah, we did have to make the hard decision that we needed to prioritize our first-party products and our API, and so this is the decision that resulted from that.
00:13:18 · Cat Wu, Lenny Rachitsky
[00:13:18] S0: So we've been seeing a lot of demand for Claude, and we've been working very hard to both scale our infrastructure and also to make our harness more token efficient so that you can get more usage out of it. It wasn't designed for third-party products, which have different usage patterns than our first-party ones. We spent a bunch of time trying to figure out what is the most seamless transition that we can offer, and so I was very happy to be able to say that everyone gets some credits alongside their subscription. But yeah, we did have to make the hard decision that we needed to prioritize our first-party products and our API, and so this is the decision that resulted from that. [00:14:01] S1: Yeah. To me, it makes so much sense. You guys are subsidizing this usage at 200 bucks a month and it's basically unlimited use of this. And I think people don't understand. Businesses are trying to make money. We're trying to be profitable here. We can't just give away compute when it's so in demand. So I get it. Coming back to the PM team, what does just the PM team look like at Anthropic? How many PMs are there? How are they kind of organized?
00:14:26 · Cat Wu
[00:14:26] S0: Yeah, so we have a few PM teams. I think we're maybe around 30 or 40 PMs right now. So we have the research PM team who Diane leads, and this team is responsible for understanding all of the feedback from our customers for our models, and then feeding that to the best research team to act on it, and they also shepherd the model launch. There's the Claude developer platform team that maintains the APIs that Claude Code is built on top of, and they also release things like Managed Agents, which is a way for you to build your agents and we can host it on your behalf. And then there's Claude Code that works on both Claude Code and the Cowork core products. There's enterprise that helps make Claude Code and Cowork easier to adopt for all of our enterprise customers, and so this is everything from cost controls, our back security controls, and just making sure that these enterprises feel very confident and comfortable using our tools. And then we also have our growth team that is responsible for growing across our entire product suite. So we work very closely with them on Claude Code and Cowork growth. And I know they also work with our other teams on CDP growth, so growth of people who use the Claude API.
00:15:43 · Lenny Rachitsky
[00:15:43] S1: So speaking of growth, so Amol was just on the podcast. You have this really interesting insight that most people haven't been sharing. There's always this sense that we need fewer PMs in the future. Why do we need PMs? Engineers can do ship. His take is that because engineers are moving so fast, PMs and designers are squeezed. There's less time to stay on top of everything that is happening. There's a feature shipping every day. So his take is he needs more PMs because it's hard to keep up. What's your take there? Do you feel like there'll be an increase in hiring of PMs? What do you think is going on with the PM profession long-term?