Lenny Rachitsky: preference

Transcript context

…Let's catch up with Latch It. So as a refresher for you who forgot. Latch It are building this tool for artisans, they want to help them sell with the community networking features like you might find on Substack. And they've identified their differentiation, they've identified their approach now using magic lenses. And all of this is going to come together to create a founding hypothesis. So if we help Artisans solve online sales growth with a social sales app, and then they've also got their backup plan. A social sales app. Then, they've also got their backup plan, or we could build the full stack solution if that doesn't work. We believe they're going to choose it over Shopify and Etsy because our solution is cooperative and easy to use. In this single sentence, we've laid bare their strategy, and now they're going to try to find out does that work? That is so cool. The output of the sprint is the founding hypothesis. I love that the term hypothesis is a part of this because it's not telling you this will work. It's this is the thing you will now test. Absolutely. Every project has at its core ... Every new product has at its core a hypothesis. There is a founding hypothesis. It's just usually not explicit. It's usually hidden, and different people on the team may have different ideas about what it is. Because it's not explicit, it's very hard to interrogate it and test it and find out if the different variables in it are the right variables.…

Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.