3 ms·

> You cannot write a small MVP of a browser, an operating system, a search engine, a game engine, a 3D modeling suite, etc I don't think that's true at all. Yo

> You cannot write a small MVP of a browser, an operating system, a search engine, a game engine, a 3D modeling suite, etc I don't think that's true at all. You absolutely can and should build an MVP of all these things. You certainly could release an MVP search engine (or even a browser-based game). You probably can't hope to gain traction at large with an MVP browser or operating system, but you can start using these things internally and dogfooding them. IMO, iterative development isn't necessarily about releasing something fast to the public, it's about rapidly building a working version that you can interact with, test properly as a whole working system and show people, so you can quickly figure out what are the most obvious issues to address and improvements to make. You can test this software internally, show it to your friends, have a small private beta or even hire testers depending on your project and budget. This is in contrast to a more traditional/naive development model where the team isn't even trying to have a working/testable version, and instead focuses on spending weeks/months building components separately, which they hope will come together into some grand vision at the end. This approach is terrible because things likely won't come together seamlessly. The different components can fit together poorly, effort is wasted on features that weren't actually good ideas in hindsight, etc. Software projects developed this way are often late, overly complex and poorly designed.

rangersanger 8y ago
Completely agree with this. Previously I was a PM at a rather large (valued >1bn) sales software organization. I was tasked with building a completely new product to replace the original product. We built an MVP and had our internal sales team use it. It wasn't easy, it took some motivation to get them to use it over the large, steady, enterprise solution they were used to. But, they used it enough that we received considerable feedback that we rolled into the public beta, which was much bigger than an MVP.
davidjnelson 8y ago
I agree. If you look at the book The Lean Startup, it’s pretty hilarious how hacks like skipping player movement animations led to a “teleport” effect for the imvu product that users loved. That’s a great example of mvp working - they didn’t know what the customer wanted, and the customer actually preferred the hacky shortcut.

rangersanger 8y ago

Completely agree with this. Previously I was a PM at a rather large (valued >1bn) sales software organization. I was tasked with building a completely new product to replace the original product. We built an MVP and had our internal sales team use it. It wasn't easy, it took some motivation to get them to use it over the large, steady, enterprise solution they were used to. But, they used it enough that we received considerable feedback that we rolled into the public beta, which was much bigger than an MVP.

davidjnelson 8y ago

I agree. If you look at the book The Lean Startup, it’s pretty hilarious how hacks like skipping player movement animations led to a “teleport” effect for the imvu product that users loved. That’s a great example of mvp working - they didn’t know what the customer wanted, and the customer actually preferred the hacky shortcut.