Minimum Viable Product and Minimum Viable Addition to a MVP

Invariably whenever I coach Product Managers and Product Owners, topic of Minimum Viable Product (MVP) comes up.  So, what is MVP? How you move forward once MVP proved itself viable?

Let’s try to explore the answers to these questions.  In my view there are at least two ways to visualize a product. The first view emphasizes the engineering view while second one is from business perspective. In engineering view a product can be considered a pyramid shaped structure in which bottom consists of functionality. As you move up connection with higher human needs keep on increasing.

The business view focuses on Value.

The Functional aspects of a MVP in engineering view get higher attention.

On the other side, in Business view, value takes precedence over any other thing.

To reconcile engineering and business view of MVP both stakeholders need to ask few questions and agree upon their answers:

a. Which functionality can I build into the MVP?
b. What is the minimum functionality to provide some value?
c. What version of my product can I build that captures most of the value?
d. How can I validate my value proposition?

Now you have a MVP and customer wants more of it. Now the question arises what to add into MVP so that it delivers the maximum value in present without compromising the near future technical and business viability.