Minimum Viable Product

The idea of a Minimum Viable Product is that you want to meet the most basic specs for your product as quickly as possible, leaving out any and all unnecessary or unimportant details. The benefits of this are a quicker test of the viability of the product, a better implementation of the core features without any extra overhead, and freedom to change your ideas quickly and without having to manage extra dependencies or features.

“what is the skateboard for this idea?” ... it immediately reframes the discussion around finding the heart of a product request. It helps teams find the simpler version of any idea to start with, if it exists.[4]


Let's say you wanted to build a blog. There are lots of features you might consider doing for this:

Etc. To get a project like this up and running, we want to figure out which of these on this list are the most important for a functioning blog. Not the best blog, not a great blog, but one that does exactly what is expected of a blog and nothing more. Let's determine what those features are:

Essentially, we are paring this down to the most rudimentary CRUD app, making our development process much more lean and nimble.


While working on your MVP, some choices may make your process more enjoyable or simple than others. For instance, spinning up a whole MongoDB or MySQL instance for a small project may be unnecessary for a quick implementation. Or you just don't want to look at default user styles on the browser the whole time. These tools, mainly for web development, will make life just a little better and maybe implementation a little quicker.


  4. The Skateboard Mindset in Product Development
Incoming Links

Last modified: 202401040446