Evidence receipt / recommendation
Published · transcript-backedSachin Kansal: recommendation
1 Jun 2025 Lenny's Podcast Why Uber’s CPO delivers food on weekends | Sachin Kansal
“No, this is not about mindlessly shipping, but once you know that you're working on something that is important, that is solving a problem, it could be a big feature or a small feature, then you have to cut down the cycle time.”
Source trail
Everything needed to verify it.
- Speaker
- Sachin Kansal
- Attribution
- Verified speaker
- Claim type
- recommendation
- Recorded
- 1 Jun 2025
- Publisher
- Lenny's Podcast
Transcript context
…Awesome. So the advice there is just find a way, get as close as you can. You may not be able to ride an Uber, drive an Uber car, get an Uber ride, but there's some way you can get really close. You may not be exactly do the thing. Awesome. Okay. I'm going to go in a different direction and there's another theme that came up again and again when I was asking people about you and what you're amazing at. And a motto came up again and again it was ship, ship, ship. Talk about that. Why is this motto, this way of working so important to you? Why is it something you try to encourage everyone to always think about? I think it's actually a natural extension of what we just talked about. If we are going to go dogfood and experience this pain and you're going to document it, what's next? You have to ship this. I'm a big believer in you don't ship documents, you don't ship brainstorming meetings, you don't even ship designs in a Figma. What you ship is code in your product. That is the only thing that actually ultimately has impact on the end user. So as I mentioned before, I develop a sense of impatience. It's a positive impatience if you will, that, "Okay, I just observed a problem for our riders or for our drivers. They have to get a solution to that as soon as possible." And for that, you have to ship, ship, ship. Now, you could interpret ship, ship, ship to be just mindlessly shipping. No, this is not about mindlessly shipping, but once you know that you're working on something that is important, that is solving a problem, it could be a big feature or a small feature, then you have to cut down the cycle time. My biggest enemy is the cycle time of we know it is a good thing all the way to our users seeing it, you have to minimize that time. So that's why ship, ship, ship has become such a motto for me and we try to do a lot of things internally operationally for us to enable that. And I'll say we still are not there. In my opinion, I think we can still be faster, we can still cut a lot of that cycle time, but we are on a constant quest to get as good as we can. What does this look like in practice other than just reminding people, "Ship, ship, ship. Ship, ship, ship." Just repeating this mantra. How do you help people ship faster, to your point, not just work all night and all day, staying long hours, just what are some ways to actually operationalize this?…
Stored transcript either side of the excerpt. The highlighted words are the published quote; the surrounding text is unedited source, never generated.