Minimum Viable Products
There was a time when I blogged regularly, and like so many others, I fell out of the habit. But I still wanted to share my knowledge, and so I tasked myself with figuring out the easiest way I can continue to contribute to the community.
As a result, I decided that short, 3 to 5 minutes video blogs are the best way for me to not only commit to weekly blogs, but also give the viewer something to easily digest. So here it is, my first video blog!
In this video, I talk about the concept of a Minimum Viable Products, and how important it is to be able to laser focus your prototypes so you can get to market quickly, and start validating your ideas.
Truth is, and I’m guilty of this too, it’s very easy to consider something you are working on to “not be ready for release,” or needing “one more feature.” This is a trap which will continually delay your launch, and sometimes even permanently stall out development.
The idea behind the Minimum Viable Product is quite straight forward. Figure out the fewest number of features your product can contain, while still being useful to your target audience. Limiting the scope to fewer features helps in a few ways
- Unnecessary development is prevented
- The user isn’t overwhelmed with new features
- Instead of spending time building what you think your customer wants, you can start iterating on your product based on the feedback the customer actually gives.
Another interesting note: The more time you spend developing certain features, the less likely you are to give up on them. The end result here, you may become reluctant to give up on certain features, even if none of your customers use it, only because of the time you spent developing it.
Take some time to watch the video and learn more!