Skip to main content

No MVP without a Customer

I've been around agilist and SW devs that are using the term MVP quite a lot these days.  And when we get deeper into the conversation I learn that the thing there are referring to is not at all an MVP.
It's not the box - it is the Star!

Perhaps we need a better term.  Perhaps we should define the terms we are using.  Perhaps we should just use the tools we have to find the better term.   Or I could just tell you - the better term is MBI - Minimum Business Increment.

Why does MVP not suffice?  Because to have a product one needs a customer that has paid for said product.  And the purpose of the MVP was to learn for actual customers about how they liked our product and if we should change it in any way.  It was also a test of our current business model, and an opportunity to learn about our business model (was it efficient, could we optimize it in some way, etc.).

Most MVPs I've discussed with people have no customers - there is no exchange of value.  Therefore there cannot be a product.

What we have is much better defined by the term MBI.  Read about it.  And a very good modern definition of MVP on LeanStack.com is also valuable to know.

"An MBI is the smallest piece of functionality that can be delivered that has value to the business in that it:

  • Adds value for the customers of the business
  • Provides valuable feedback that the right functionality is being built
  • Provides valuable feedback that the functionality is being built the right way
  • Provides functionality that can be verified as an increment that can be delivered
  • Enhances the ability of the organization to deliver value in the future"
Both are about delivering value.  Yet one is value delivered to the business (an internal measure) and the other is value delivered to a customer (external measure).

Comments

Anonymous said…
I think this MBI concept might help in the products/features my team is working on ... thanks for the post!