<Back

From concept to MVP

Imagine that we want to create an effective habit tracker. After a comprehensive study of competitors and other marketing research, mission statement, and ideas, we came to our final concept: "iOS & Android mobile application that will allow you to maintain a database of habits and will write off 1000 rubles for every second habit pass."

The concept is there, now it's time to think about what an MVP should look like.

MVP is the minimum viable product. If you go into details, then MVP is a product that has a minimal implementation of key functionality that makes the product suitable for use and, in particular, for its sale.

Based on the experience of working with entrepreneurs, startups, and with their projects, the first MVP concept will contain the following functionality:

1. Add/Remove/edit habits from anywhere in the app;

2. Widgets to see how many habits are left to perform;

3. Hundreds of different reminders about the time of the habit, about the promotion, about the birthday of the father of the founder of the project, etc.

4. Connect 100 payment systems so that even the Khoisan people can pay for the missed habit.

5. Statistics with extensive detail.

And another 100500 chips, which seem to be an integral part of the product.

And then it's time to reflect. The key question of our reflection is: "Why do I need this function?".

Before asking this question, it is necessary to identify what is the most important thing in the product and what functions are necessary to implement the most important thing.

This process looks like this:

1. What is the key functionality in my product that is the point of difference from competitors? 

In the case of our solution tracker, this is a write—off of 1000 rubles. for an expired habit. Now our main task is to make the most minimal functionality for its operation.

2. What does it take to make the key functionality work?

— Internet acquiring is the heart of the key functionality.

— The ability to add habits so that there is something to write off money for.

— Notification of the need to perform a habit in order not to look like robbers.

— Functions required according to store guidelines. For example, deleting an account.

Great! We have decided on the functions that are vital for our solution tracker.

3. We did everything smoothly, but more often after point 2 it is required to run through the functions several times with the question: "Why do I need this function?". And if there is even the slightest hint of the answer "there is no need", then this function should be eliminated, or reduced to something simpler.

We have decided on the minimum that we need to implement. But there is one more component that needs to be worked out — the implementation period of the MVP. We will talk about it in the next publication.