Jul 29, 2020

Reader question: Do we need to build MVP for every product?

Hi Budi, the way I see Minimum Viable Product (MVP) is a minimum product with minimum requirement to test to the users. Is it true? If so, do we need to build MVP for every product that we’ll build? – Sandy

Hi Sandy,

MVP gets popular in the industry, for good reasons. The idea of MVP is to validate the hypothesis we have as cheaply as possible.

Imagine if you want to build a new product, mainly the primary question is: Does anyone want to buy or use this product?

With MVP, we’re basically saying, let’s not build the real product just yet because we don’t know if people even want to buy or use this. Instead, let’s build a prototype to test our hypothesis. One of the most popular stories was from Dropbox. Drew Houston, the co-founder of Dropbox setting up a simple video and sign up form to join the waiting list.

In that video, Dropbox as a product is not yet ready to be used for a large number of users. Probably still have lots of bugs. But, by doing that, Dropbox validates an important value hypothesis: Does anyone interested to use this? And this can be measured by how many people are actually signing up the waiting list to see how many people are interested.

Now, for your second point, do you need to make MVP everytime your team builds a new product? I’d say, yes in most cases. Just to name a few top reasons for startups to fail: no market need (42%), ran out of cash (29%), get outcompeted (19%).1

MVP reduces the risk of failing greatly. You should read this book: Lean Startup, by Erick Ries if you want to dive deeper into this topic.

Thanks for the question! Hope this helps! P.S. If you want to send a reader question, please feel free to send email


Footnotes:

  1. CB INSIGHT - The top 20 reasons startup fail.

2020

2019

2018

2020

Sep 17

Entering product design – Chapter 4: Product designer key skill areas

Sep 14

Entering product design – Chapter 3: Misunderstanding of business

Sep 11

Entering product design – Chapter 2: Principles over steps

Sep 10

Entering product design – Chapter 1: Silver bullet

Sep 10

Entering product design – Overview

Sep 04

SAR: A framework for concise storytelling

Aug 27

Start your design with outcome

Aug 24

New medium post: Collaboration ground for design systems

Aug 17

Action points

Aug 13

Pulse check: Listen to your team

Aug 11

You should actively apply for a new job

Aug 10

Design systems' area of influence: Service (3/3)

Aug 04

Design systems' area of influence: Offering (2/3)

Aug 03

Design systems' area of influence: Identity (1/3)

Aug 01

My mom ran me to the hospital

Jul 29

Reader question: Do we need to build MVP for every product?

Jul 27

Reader question: Do I need formal design education?

Jul 24

Recognize assumptions

Jul 21

Sandbox for your personal growth

Jul 20

Start your week with questions

Jul 17

Specificity in feedback

Jul 15

Don't sell the design. Sell the business impact

Jul 14

Overwhelming inspiration

Jul 13

The framing trap

Jul 10

Everyone vs. Specific

Jul 09

The blind horse designer

Jul 08

Set the context in your meeting

Jul 07

Let's just try and see what happens

Jul 06

Managing expectation

Jul 05

Low UX maturity company

Jun 17

A simple exercise for career reflection

May 31

The “Coach sheet” – A paper-based system for people management

May 26

Bring calm to your remote team

Feb 13

Workshops can be more efficient than meetings

Feb 07

3 questions designers should be asking

Feb 06

Walking 1on1: A refreshing way to connect

2019

Nov 21

My hope for stubborn 'Innovators'

Jul 18

Five simple actions to help you gain more time

Apr 23

Evolving Product Experience Principles at Bukalapak

Mar 09

A framework to give better design feedback: Analyze, Discuss, Suggest

Jan 28

Making a decision is hard, here's my rule of thumb

2018

Dec 04

Essential skills for Product Designers

Nov 16

Quick life update

Nov 06

Things I learned from working at Shopify

Oct 15

About design critique

Sep 17

Common icon design problems you should avoid

Sep 06

Preface: Welcome to yellowstroke.com