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
15 published records
01 / recommendation
“So we wrote Building Rocketships to help people figure out how to build not only great products, but companies that build great products to make sure that people who have the knowledge not to be one hit wonders and the book is divided into two.”
02 / belief
“We spoke earlier and I have a whole thing about ethics of AI, et cetera. And I think that we have a responsibility as product people, and I'm seeing PMs ask the questions that we didn't get to see them ask when we were building social media.”
03 / belief
“I think Oji started... He laid the foundation when he said it's day one and when you are working and thinking about building product in this type of era or space, it's important that you remember that.”
04 / belief
“I think that having a call to action for our PMs to really be thoughtful about what it is they're building and what it is they're integrating into their product is really important to us.”
05 / belief
“I think some of these lessons, especially that last one, is the kind of lesson that you can hear it and be like, "Yeah, yeah, I get it.”
06 / recommendation
“The reality is, and my experience has shown that, you're better off picking an opinion, shipping it out there, being wrong, and then adjusting than leaving too many options because you then can never learn what was the better experience overall.”
07 / evaluation
“There's talk recently of just PMs are almost becoming the bottleneck for teams because engineers are moving so much faster and PMs are the same, just like sitting or maybe docs are easier to write.”
08 / prediction
“PM takes this amount of time, developers takes this amount of time, go-to-market takes this amount of time. And I think that contract is basically exploding because the build process, the closed solutionary process, the build process is accelerating so fast.”
09 / recommendation
“What I love about this is this is something that I've seen a bunch is having a very specific problem to solve for yourself is a really good way to build and get into these tools because you're motivated to solve a problem and it's a specific thing that you're doing versus just generally, "I'm going to go sit around and play with Lovable.”
10 / recommendation
“" For example, or you like reading and you actually have a database of the entire Austin library or whatever it is online and you can pull it if you really want to and it can recommend based on your feelings.”
11 / evaluation
“We've seen a lot of companies want to do so many things and expect LLMs to be as broad as the problem sets they want to solve for. And we in our experience have seen that to do that you actually will need to have specialized first and then create a layer of a connective tissue that can offer intelligence.”
12 / recommendation
“They'll build applications that just works with them. And the advice for PMs is that we should be the vanguard of that because if we can start doing that for ourselves, we'll be able to do that for software that hits a million people because that's the way to get started.”
13 / recommendation
“I think there are things you need to learn about the sources of competitive advantage and even what that means like intellectual property or economies of scale, economies of scope.”
14 / evaluation
“When you think about it that way, there is a conflict between the CPO and the CTO that actually drives innovation in my opinion, because one person is trying to optimize the resourcing, the fixed, right?”
15 / evaluation
“One of the things I learned from failing a lot at building companies is that sometimes the way that YCO, the people pitch it, is that you build something and if it doesn't work, you pivot, da-da-da, stuff like that.”