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
26 published records
01 / recommendation
“And you might have a lot of conversations and have a slightly larger team and might take you 12. So we like to spread it out over two days, do two four to six-hour blocks.”
02 / evaluation
“You shared this in my newsletter and I was just looking at it, and that excerpt, that post is amongst the top 10 most popular posts of all time in my newsletter, which is especially special because it's not an AI-oriented, it's one of the few non-AI posts that are near the top 10, which just tells me how valuable this is to people.”
03 / recommendation
“The very beginning of your project, we recommend this kind of crazy idea that you clear your calendar.”
04 / belief
“We believe product teams should focus engineering efforts and competitive advantages, not integrations.”
05 / uncertainty
“Maybe a last nugget or something you want to, I don't know, just double down on to leave folks with before we wrap up.”
06 / belief
“We haven't finished actually going through the process. I think we're towards the tail end of it.”
07 / belief
“Week after week you're learning, but you're also really able to track exactly what is it that we learned and how does that affect our strategy.”
08 / uncertainty
“Anything more you can add here for helping people start to think about ways to differentiate beyond the obvious price and speed. And I don't know, a couple more.”
09 / belief
“By doing a combination of vibe coding, real coding, all of which is based off of pencil sketches, we can go back and see the sketches he's doing on paper to define this is what I think needs to be in there to make this compelling to deliver on my differentiation, and then he's using a product video so that the entire thing doesn't have to work fully freeform.”
10 / belief
“Before you do that actually, let me ask you a question here. Because I think people seeing this could think, "Oh, this is like...”
11 / belief
“I feel like it's actually more helpful to engineers, like non-product people, because I think a PM my brain would be like, I want to do this intuitively.”
12 / belief
“I think there's sort of a humorous one for Mellow where it's like, which founder is like, "F yeah, that's exactly what I want to build.”
13 / belief
“Obviously you could also read the book. That goes through a lot of this process, but I think the template is just like a plug and play.”
14 / belief
“Something that is a common question I think for founders is price as a differentiator.”
15 / evaluation
“In this case, they interviewed four customers. Well, it looks like this is the right customer.”
16 / evaluation
“I just had this naming expert on the podcast who names some of the biggest companies in the world, Pentium, Powerbook, Sonos, Purcell, and that's their approach is they used to do brainstorms. He's like, that doesn't work.”
17 / recommendation
“How do I actually describe what the product is, how it's differentiated?" It's one of the reasons why doing the foundation sprint first and then doing a design sprint can really help you, because it allows you to spend time working on that harder part of what it means to design and build a product.”
18 / recommendation
“Essentially his feedback is, wait as long as possible to start any sort of sketch or prototype, because as soon as you start drawing what you're building, now everything you do will be a response to that.”
19 / preference
“It's going to be a really compelling reason for us to not go with just the one that renders faster or the one that gets the user to their benefit with one less click. And this notion that you can have a decision-making guide, we think we've seen it be so useful for us in those contexts.”
20 / preference
“I love that the term hypothesis is a part of this because it's not telling you this will work.”
21 / evaluation
“I think for a lot of folks though, it can sound like this is just elementary, differentiation.”
22 / recommendation
“Who's the most important customer, for example, is the first question, the very first question that a team needs to answer. And as we do that, just as an important side note, we're using this tactic that we call work alone together.”
23 / recommendation
“We cleared our calendars for the week, and we created a prototype of this, this thing because we decided, look, we're never going to get anywhere.”
24 / recommendation
“We know customers can understand these and they create a great starting place for your team to think about differentiation because you can quickly look at this list and start scoring where you think your product could be on these scales and you know that if you can use one of these, people will understand it.”
25 / recommendation
“Once you've got that founding hypothesis, then you're going to go and do design sprints, and we recommend you clear the calendar for two to three weeks at least, so you have the chance to be wrong about your hypothesis.”
26 / evaluation
“So the basics is really the context for thinking about differentiation. And differentiation is the heart of what we're doing in the foundation sprint because it goes without saying perhaps, but we like to say it.”