Always better for startups to do lots of small launches vs 1 large launch. Even though this approach will usually take a lot more time.
1. Product will start w/ bugs. Easier to find in a small launch.
2. Don’t know if customers want what you’re building until they can use it.
Transcription
Hello, everyone. Today, we’re talking about launches. It’s almost always better for a start-up to do lots of small launches rather than aim for one large launch, even though taking the more iterative approach will appear to take more time. It’s absolutely worth it. I like to be proud of my work too, so I understand the desire to ship something a little more polished something that perhaps might give the user a little bit more value. But Jack Dorsey the founder and CEO of 2 public companies once said “if you’re happy with a release you’ve waited too long”. So here are the two reasons why you should ship new versions early and often:
1: Your first version of a new product or feature will have lots of bugs often strange and unpredictable bugs that will only be visible with customer feedback. Not only these bugs easier to find and fix it in small launches large launches, with much fanfare, are often hurt by these kinds of bugs.
2: Your ideas for this product or feature are only a hypothesis until a customer actually tries it all the data domain expertise and user interviews in the whole world will not guarantee a customer who needs your solution. The sooner we get your product to a customer the sooner we find out if they really need it what you need to fix on it to actually solve their problem and how to make them happy.
