Task: About your MVP

It's important that we only start building our MVP (Minimum Viable Product) after we are done with customer development. If you are not done with stages Customer Development and Unique Value Proposition, then you could consider going back to finish it so you avoid the risk of building a product no one needs! Ouch!

The reasons are:

1. You might be building a product with the wrong features that doesn't fufill the UVP.

2. You might be building for a problem nobody has.

3. You might be buliding the wrong solution for the right problem.

MVP doesn't mean half-baked. it means the perfect version of something just enough to deliver the solutionMVP means that this product has only the key features that your customers need in order to solve their #1 problems. 

It's best to start with no features, and start from there. Don't include nice-to-haves and bonus features.

After you build your MVP, focus your energy on learning about your customers, and not about optimization. Before you understand your customers fully, you could be optimizing for a wrong solution. At this point, think macro before micro.

Another practice to also remember is to deploy continuously. This is the methodology of releasing very frequently – as frequent as several times a day. Deploy any full feature that your users can use as soon as you are ready. We need to conduct as many experiments as possible.

Continuous Deployment