4 ms·
Which one of those two options do you feel is the one more likely to fail?
by AVTizzle 13y ago
Which one of those two options do you feel is the one more likely to fail?
- Jormundir 13y agoI hoped it was obvious: There are huge advantages to having a small idea. There's a clear MVP, a clear short term goal to achieve. This has a big effect on morale: the developing team has a series of short development bursts ending with an achievement and the vision of the company in eyesight. The quality of the product tends to be higher sheerly out of being simpler. A small idea can have very wide reach, and can be an essential need to users, or a new pillar of infrastructure. Often after building a small and strong product, a company has the freedom to apply and maximize it for the full range of possible use cases. The easy example is Google, but I like to use the StackExchange network. They started with a Q&A site for software engineers, and once that was successful they expanded to a huge range of fields. Huge ideas often send startups down a path to failure. Morale gets drained over time as features get completed but the vision remains too far away. Complexity increases greatly, and the core product gravitates to unmanageability as it grows. Even a best in class engineering team can be toppled by the exponential complexity of a large product, there's a potter's field of large products being built by awesome engineers, in big companies and small. I could go on and on for each side, but the main point is, having a company vision that is the MVP is amazingly powerful, and opposite, having a company vision that is massive even with an MVP that is a stepping stone on the way to the massive vision, is a swamp to trudge through for years.