Cut scope, not quality

The way to cut down on time is when time is being pressured downward, a lot of times engineers, PMs, designers, they will cut on quality rather than cutting on scope. And actually you can cut on scope.

We look at every element that's going to take any time to build and we just say, what if we remove this? Is the product still useful? And we keep repeating that until we remove whatever's left and we say it's going to be useless at this point.

If that's not useful, then anything else built on top of that is also useless.

Start small with everything. If you try to boil the ocean to make a cup of tea, you'll never get there. So if you're making a cup of tea, just make the cup of tea. You don't need to boil all the water that there is.

Build the scooter, not the axle. So if you're trying to build the minimum viable product for a car, don't build just the wheels and the axle, build the scooter first. And then from there, you build the bicycle, and the motorcycle, and then the car.

For a new launch, you got quality, features, deadline, choose two. The beautiful thing about software is you can keep iterating on it. So it's not like a physical product where you have to always have quality in there, otherwise it's never going to have quality.