Minimum Viable Product

When we create a new product, Product managers always grapple with the problem of when to take the product for customer validation.

Taking it too soon would be the prospects are not interested in what is being demonstrated. Taking it too late means that we could be grossly wrong and any feedback that comes could not be that valuable.

Another problem is taking it to all the prospects might lead to unsatisfactory comments on how the product is still not complete.

How do we manage thing timing issue?

A simple concept of minimum viable product could help us understand when is the right time to start the demonstrations.

Minimum viable product is the core product that satisfies the needs of a chosen subset of the target audience. It has just enough for us to focus on a subset of prospects, validate understanding and move on.

What it is not

MVP is often misunderstood as a the bare minimum of a product that can be developed. This understanding is incorrect.

The emphasis is on viable and not on minimum.

The approach of MVP is to make sure we target smaller groups, validate our product and keep adding to it as we keep moving.

The minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.

Hope this helps.

For more reading , check out The Lean Startup: How Constant Innovation Creates Radically Successful Businesses

Comments

Principles for developing systems that are anti-fragile

I have been trying to make sense of what anti-fragility means and how do I use that in my day job. As a Business Principal, I tend to work with the abstract but orchestrate a program of work that needs details. This makes my job a little difficult in the terms of designing for more self-preserving systems that preserve the spirit of the abstracted strategy or vision. I came across an article from Daniel Russo on anti-fragility and his attempt at creating a manifesto similar to the manifesto for agile software development. For more reading on Daniel Russo, here is his profile: http://djrusso.github.io More reading from his paper here: https://www.sciencedirect.com/science/article/pii/S1877050916302290 This post is an attempt for me to understand what goes into developing a program that uses every opportunity to strengthen itself and achieve its objective - the vision. I liked the approach of principles for developing systems that are anti-fragile. It i...

My Journey in Inquiry and Advocacy - An experience report

It is recently that I have consciously started practicing Inquiry. Let me explain. I am a consultant who constantly looks at the situation and comes up and implements the solution to progress from there. While I do that, I constantly use Inquiry as a means to progress - one of the key facilitation technique specifically in multiple stakeholder situations.

A Business Principal's guide to Machine Learning - The origins

As a Business Principal, I have been coming across the term Machine learning for a long time. Several business executives have wondered what this animal is and how does it help them. The series of posts is to list out what Machine learning means to a business principal and some basic industry standard approaches that has been tried out in the past few years.

Life of a Business Principal in Consulting

Search This Blog