Lenny's Podcast / episode intelligence
Speakers in the public record
Claim mix
Evidence policy
Every row below preserves an exact excerpt. Identified speakers are linked; unresolved voices are labeled and excluded from people counts.
Claim ledger
28 published records
01 / recommendation
“In the product space, probably things like High Output Management or The Design of Everyday Things, or those kind of classic type things because I think they're extremely applicable in AI.”
02 / belief
“For a while, there was this... I think there was a company-wide stand-up because we disbanded all teams.”
03 / belief
“One analogy that someone at OpenAI who I really respect, he's like, "We're kind of like Disney, where Disney has this one kind of creative IP, which is their content, and they have cruises and they have theme parks and they have comics and they have all these different things." And I think we have amazing models, but there's all these different ways that you can productize them and we kind of just have to maximize the impact in all these different ways.”
04 / evaluation
“Whether it was right or wrong, it is now the fastest-growing, insane revenue generating business in the world.”
05 / belief
“Definitely don't bring me on here as a pricing expert, I think you have got better people for that.”
06 / uncertainty
“I don't know, is there a philosophy book you're like, "Here's the one to read if you're getting into this.”
07 / belief
“I think we were really lucky with ChatGPT that that happened where there's just users sharing use cases with other users everywhere.”
08 / belief
“I think you've got to do a little bit of sci-fi to be in this space. You shouldn't copy any of it, but I think you learn from it.”
09 / evaluation
“I think you do need some ML knowledge, I'm afraid. But for product and engineering and design people, and those kinds of functions, I actually think that if you are just curious about the stuff works, it doesn't matter at all if you've never done it before.”
10 / belief
“I think you were planning to do this as your main thing and then you somehow took the side quest.”
11 / observation
“The benchmarks are increasingly saturated. So really you need real-world scenarios where your product or model is not actually doing the thing it was supposed to do, and the only way you get that is by shipping, because you get back to use case distribution and you can make those things good.”
12 / belief
“The amount of questions you have to grapple with are truly super interesting. And philosophy, it's not a traditionally practical skill, but it does really teach you to think things through from scratch and to articulate a point of view, and I think that has come in handy numerous times.”
13 / uncertainty
“Wow. This is such a good example of, I don't know if you think of it this way, but when someone offers you a seat on a rocket ship, don't ask which seat.”
14 / belief
“I think people are actually just getting used to this technology in a really interesting way, where I find, and this is why the product needs to evolve too, that this idea of delegating to an AI, it's not natural to most people.”
15 / uncertainty
“I don't know how to exactly describe the OpenAI launch cadence, but you've got to set yourself up in a way that is sustainable.”
16 / belief
“I think we had this intuition from the beginning, but we never got to it because we didn't have enough GPU or other constraint to really go do that.”
17 / commitment
“Now I'm in some for fun bands and we will kick from time to time. It's like the one thing I can do when I'm otherwise super tired and can't think anymore because it balances me out in good ways.”
18 / belief
“There's two acronyms people have been using for this specific skill of AI driven SEO. I think one is AEO, which is answer engine optimization.”
19 / preference
“Before I built the product team, I actually built the data science team because I was getting frustrated.”
20 / preference
“I think that's been really true for our recruiting too where we try to maximize the number of empowered people who can ship because that's how you have a small team and still get the ton done. So there's a couple of things, and I spent a lot of time on vibes too with each team because I think one of the things that is challenging when you try to do research and product together is that the cultures are different.”
21 / evaluation
“I think shipping really funky capabilities before they were polished is another thing where that feels like a tactical decision, but it became a playbook because we would learn so much.”
22 / prediction
“I think there really is a world where, as this thing hits a billion user scale, it can get you distribution, it can get you started on making something in the same way that people built on the internet and there was entirely new businesses to be built.”
23 / evaluation
“SOC 2 doesn't get better with [inaudible 01:04:48] models, but I think for many of the core capabilities, that's a good litmus test. So I've always found you really have to lean into why is this place successful and then maximally accelerate that, so to speak, because it's what allows you to turn something that feels like an accident into something that is a repeatable label.”
24 / prediction
“Because many companies, I think, if they have a subscription model like us, they would gate it behind their paid plan.”
25 / evaluation
“It's embarrassing, but that's strictly less bad than not getting the feedback you wanted." So I think just approaching each scenario from scratch is so important in this space because there is no analogy for what we're building.”
26 / recommendation
“Because if you have tech that's, for example, GPT-5 is really, really good at front-end coding now, I think that means you've got to reprioritize it.”
27 / commitment
“Obviously, at some point, that doesn't scale, but I always felt like part of my role here, obviously, was to think about the direction of the product, but also to just set the pace and the resting heartbeat for our teams. And again, this is important anywhere, but it's especially important when the only way to find out what people like and what's valuable is to bring it into the external world.”
28 / preference
“You don't know if people are going to like it, that's always empirical, but you know what it can do. And with AI, because I think so much of it is emergent, you actually really need to stop and listen after you launch something and then iterate on the things people are trying to do and on the things that aren't quite working yet.”