What is an MVP

The traditional MVP, the Minimum Viable Product, is a product which has the minimum functionality which lets you test out the viability of a product or a business idea in the market, among its intended customers.

We should focus on the value that can provide our product to our customers. So MVP should be Minimum Valuable Product

How to build an MVP?

I’m sure everyone reading this article knows the Build-Measure-Learn feedback loop coined by Eric Ries in the Lean Startup Methodology.

So we have to focus first Why we are building and then What we are building.

So in the MVP framework, the order of priority of M, V & P, is thus not as straightforward as their appearance in the acronym.

How to find Value?

The answer is simple – TALK . TO. PEOPLE.

Whether you’re building a new product or a new feature in an existing product, first list down all the assumptions, and then talk to users, current or potential. Do interviews, Survey, Market research, previous data analysis to identify people’s problems that you want to solve.

How many people should I talk to?

This is an interesting question, and there is no right answer. Based on a few internet research, for a brand new consumer product, it looks something like this.

Talk to real people, gather at least 10–12 patterns to get an idea.

Who else provides that Value?

Answer is simple. Ask question with your customer –

  • What is it that my potential customers are doing for which I have to build something better?
  • Are they using another product?
  • What is it that the user is doing today to solve their existing pain point?

And finally, Do a competitive analysis. What value the existing players are providing. Find out market share currently, they have.

How to spec the Product?

First V, then P.

Prepare a hypothesis, how you can solve your end user’s problem. List everything, note down all the features/items you want to deliver.

How to make it Minimal?

Build a pyramid with all features and set them in layers. Put your items under Functionality, Reliability, Usability, Delight layer.

Now slice through across the layer. Cut any/few items from each of the layer but never remove any complete layer. Removing any complete layer will not gonna be the actual user experience.

To summarise

#1 Find Why before What, define Value before Product.

#2 Talk to real people, gather at-least 10-12 user patterns.

#3 Study hacky and tacky user habits in action right now.

#4 List all features of product that want to deliver.

#5 Draw a product pyramid and cut a slice across layers.

Product/Feature Prioritization Framework

Based on Scoring
1. Ice
2. Rice

Based on 2*2 Metrix
1. Impact vs Effort

Based on Customer Feedback
1. Kano Model

Based on Team decision
1. Playing poker

Detail Article on Prioritization Framework will publish soon. Stay Tuned.

Thank You 🙂

Toufiq Mahmud