Lenny's Podcast: Product | Career | Growth
00:51:14 · Lenny Rachitsky, Amol Avasare
[00:51:14] S0: Yeah. And I think there's also an element of shipping to learn, building a prototype so that you can have a better opinion. A lot of people talk about just, "I'm just going to try three things, see how it goes and that'll help inform the roadmap." This is now the PRD, is look at it instead of talking about it. So there's a lot of value there still. [00:51:29] S1: That's very true. I think that's a great point. So even for me now where we've got number of PMs, we've got many engineers, there are certain times when I'm like, "I want to articulate the idea I have in my head." It's just better for me to prototype it and show it. Right? So I think that is really important. And then we are very scrappy. So we're a big company by name, valuation, but we're extremely scrappy, and just the focus internally is just minimize bureaucracy and just go. And so probably 70%, maybe 60, 70, 80% of what we ship does not have a PRD. I'm averse to PRDs. I think I just hate documentation. I'm just like, "Go, go, go. Just cut the blockers." 20, 30% of stuff where it's like, it's important, it's really important to get right. The documentation should be really good and that people should spend a lot of time on it. But by and large, I think PRDs are just outdated at this point, and you can just kick things off with a good team without needing to do that sort of thing.
00:51:29 · Amol Avasare, Lenny Rachitsky
[00:51:29] S1: That's very true. I think that's a great point. So even for me now where we've got number of PMs, we've got many engineers, there are certain times when I'm like, "I want to articulate the idea I have in my head." It's just better for me to prototype it and show it. Right? So I think that is really important. And then we are very scrappy. So we're a big company by name, valuation, but we're extremely scrappy, and just the focus internally is just minimize bureaucracy and just go. And so probably 70%, maybe 60, 70, 80% of what we ship does not have a PRD. I'm averse to PRDs. I think I just hate documentation. I'm just like, "Go, go, go. Just cut the blockers." 20, 30% of stuff where it's like, it's important, it's really important to get right. The documentation should be really good and that people should spend a lot of time on it. But by and large, I think PRDs are just outdated at this point, and you can just kick things off with a good team without needing to do that sort of thing. [00:52:34] S0: Say more about that. What do you do to help make sure, because people can build so fast, or spend a lot of time going in the wrong direction, ship things that are not what you're asking? How do you kick off a project and clarify, "Here's what we're doing"? Is it just a conversation or is there anything beyond that?
00:52:48 · Amol Avasare
[00:52:48] S1: It really depends on the size of it. And this kind of goes back to the two-week thing. So why we have that two-week thing, it's more like, how do I have some filter to say if we're investing heavily into something, we should apply more thinking behind it versus if it's a smaller set of investments, just go for it? And as a growth team, again, you do have a decent amount of these smaller things that you do. So for very small changes, like, "Oh, there's a thing coming. We need to have an upsell for it. What is it the thing we're doing?" This is just on Slack. This is just purely on Slack. It's just messages back and forth. And I think it also depends on having a good caliber of engineer in there, but engineers can understand, like, "Hey, I know you said this, but what about that for the audience?" And so we're lucky we have good product-minded engineers in that sense, but all these smaller things are very much just on Slack back and forth, and that's what you do. For the larger things, I think I very firmly believe in a proper kickoff. So we still do ... Just there's so much going on at this place. No one's got time, no one knows what's going on. And so doing a cross-functional kickoff, get legal, get safeguards, get everyone in the room and just be like, "This is what we plan to do. What do you care about? What do you care about? What do you care about?" That 30-minute meeting for larger things is just, I think, still so important to just streamline all the mess that may happen later if you don't do that work early on.
00:54:17 · Lenny Rachitsky, Amol Avasare
[00:54:17] S0: What's your approach to crafting that PRD in those cases? Is it ramble into Claude? Is it, do you have a template? [00:54:24] S1: Even in those cases, there are times I don't craft a PRD because everything's moving so quickly, right? So there's still some of those cases where I just set up the meeting and then five minutes before, I'll put it into Cowork, some of my thoughts, what credit. "Here are the things that I need to think about," spin up a basic doc and we use it to talk. Other times I won't even have a doc. But if I am creating a PRD, I have basically, a skill that they've created, and then there's projects with all the previous PRDs in there, and then it's pretty simple. It has the format down so I'll just say, "Here are the things I care about. Here's the why. Here's the problem," and flesh out the key considerations, flesh out the cross-functional stakeholders, those types of things. But again, my default is if I can avoid the doc and if we can just jump to action, then that's what we should do and increasingly just jump to prototyping the thing. [00:55:24] S0: Yeah. And that's where I think it'll get so interesting once we can automate more of that, just like your assistant talking to the legal assistant, just ironing out all these little, what's important to you, what's important to the ...
00:55:35 · Amol Avasare
[00:55:35] S1: Yes, and it's coming. And I think the legal team has done good enablement around this. We work as versions of, how do you ... You can think about how can you mimic what someone might say and set up a Claude. Right? So there's things like that, that I think that we have now. And then as Claude gets more and more context and gets better at parsing long contexts, I think these are things that Claude will just get better at knowing. One of the things, Lenny, it's a slight tangent, but one of the, I think, most effective ways I use Claude, or one of the most interesting ways I use Claude, which I see a number of people doing internally is to help you identify misalignment. This is, I think something that I found really, really helpful. So with Cowork, you have the Slack MCP, and you can tell Cowork to say basically, "Look across Slack. You know the projects that I'm working on. These are the things that are top of mind. Go and find me areas of potential misalignment right now." And it does a really, really good job. So this is something that I've scheduled runs every week. Claude's looking at things and coming back to me and saying, "Hey, I think these things you should be aware of." And so you can think about in that shipping context, it's a similar thing where Claude can basically be looking at what's happening across the company and say, "You're thinking about shipping this thing. Here's who you need to talk to. Here's what you need to keep in mind."
00:57:00 · Lenny Rachitsky
[00:57:00] S0: That is so cool. I am so excited to tell you about this season's supporting sponsor, Vanta. Vanta helps over 15,000 companies, like Cursor, Ramp, Duolingo, Snowflake, and Atlassian earn and prove trust with their customers. Teams are building and shipping products faster than ever, thanks to AI. But as a result, the amount of risk being introduced into your product and your business is higher than it's ever been. Every security leader that I talk to is feeling the increasing weight of protecting their organization, their business and not to mention, their customer data. Because things are moving so fast, they are constantly reacting, having to guess at priorities and having to make do with outdated solutions. Vanta automates compliance and risk management with over 35 security and privacy frameworks, including SOC 2, ISO 27001, and HIPAA. This helps companies get compliant fast, and stay compliant. More than ever before, trust has the power to make or break your business. Learn more at vanta.com/lenny and ... ... your business. Learn more at vanta.com/lenny. And as a listener of this podcast, you get $1,000 off Vanta. That's vanta.com/lenny. I feel like there's this like, what are the jobs of a product manager, and then how are they slowly going to be supported/done by AI? So there's this misalignment, just like fine misalignment, and then maybe one day, it'll be like, aligned people initially. You talked about this cash automation for growing, like, how do I grow this product? That's starting to happen. Another that I use myself when I'm building stuff is just asking, "How do I make this product better? How do I make this a better user experience?" And asking the AI to just give me a bunch of ideas, and they're actually really good. So it's interesting how these little pieces are starting to be put into place to do more and more of this role. I'm curious what other automations you have and your team have that are effective. What I love about these conversations is you're basically living in the future. You're working on the most bleeding edge company with the most talented people, with the most cutting edge tools. And you can see where things are going and start to actually live in the future, build things that nobody else has even thought about or can do.