This is a fantastic article. We've had a decent amount of success so far with our startup following this same mantra. Release early with a core set of features, and then follow up with rapid releases (preferably one per feature).<p>This has the following advantages:<p>1. Unnecessary features are the #1 source of waste in software. If you launch with a very limited feature set, it's much easier to avoid feature bloat.<p>2. Having customers immediately helps to fund future development, gives you a large group of real-world test cases, and a huge source of information about what the market wants in your product.<p>3. Rapid releases let you create constant buzz about your product. If you have six months between releases, it's much more difficult to create constant conversation about what you're up to. Your users will be happier, also, because they continue to feel they're getting more for their money, and they get excited about what comes next. (Also, if you implement their suggestions, they can feel more like they're participating in the product development, which builds a good customer relationship.)<p>4. Continual releases are a very powerful motivator. We've tried it both ways, and having a release every week (or every other week) for smaller feature sets is much more motivating than spacing them out over a couple months.<p>(Note: this naturally assumes you've got a SaaS model like us. However, I think you could pull off something similar with desktop software, within reason.)
When it comes to releasing products, the toughest lesson to learn is to "Go Early, Go Ugly." Most first-time entrepreneurs prefer the opposite because their DNA is to avoid rejection. Their primary focus is to seek validation, from their peers and from their mentors (in time also from their customers). In their mind, rejection is merely an undesirable outcome, which they unfortunately tend to take very personally because they think of it as a failure and a painful reminder to be more prepared the next time around. So they naturally prefer to get their product as perfect as possible. But rejection is NOT a failure. We don’t learn much from positive feedback. We learn a whole lot more from negative feedback. Entrepreneurs who avoid rejection are essentially depriving themselves of important “learning moments”. It's like learning how to sail, you don't start learning until you start to get wet. It seems obvious but for me, it was a tough lesson to learn. Good luck, everyone.
not sure I agree with this article, sure all those big companies started out small, but it was a whole other market back then.<p>The game has changed, you now need that huge feature list, you now need that top notch design etc. Why would someone use your product with all the features missing, when they can use another free product that already has those features?