Viewing entries tagged with 'minimum viable product'
In earlier articles I’ve discussed various aspects of Minimum Viable Product (which I like to refer to as MVP Tests to avoid any confusion with an actual product). In this article I’d like to say more about the critical concept of Product Market Fit.
Normally I like to keep my newsletters to discussions of organization, process and best practices that I believe apply to nearly all technology companies, and I limit the number of product-specific techniques I discuss because of that. I save the product-specific techniques for my direct work with companies so that I can be sure it's relevant.
I have written earlier about the differences between user prototypes (simulations intended to test the user experience), and live-data prototypes (actual code intended to send live traffic to in order to test real behavior). See http://www.svpg.com/product-discovery-with-live-data-prototypes/
To continue on the series of articles describing the critically important concept of Minimum Viable Product (MVP), in this article I wanted to contrast the concept of Viable Product with what I call "Minimal Product."
Earlier I expanded on the notion of Minimum Viable Product (MVP) and I promised a series of articles that explores aspects of MVP Tests that often cause product teams confusion. In this article, I’d like to discuss the relationship between the MVP Tests, Product Market Fit, and the Product Vision.
One of the most important concepts in all of software is the notion of minimum viable product (often referred to as “MVP”). But if you’ve been around software products for a while, you know that term is used in many different ways, and while the term intuitively resonates with people, there’s often a lot of confusion about what this really means in practice.