Apa yang harus dilakukan untuk mengetahui apakah MVP yang dibangun sudah viable?

Menurut Alex Iskold, sebuah MVP haruslah sederhana, namun tidak terlalu sederhana, harus mencukupi kebutuhan. Maka dari itu, sebuah MVP dikatakan viable, adalah saat dimana MVP tersebut memiliki fitur yang sedikit, namun saling berfungsi satu sama lain.

Untuk mengetahui tingkat "just right" dari sebuah MVP, adalah:

1. Brainstorming terkait fitur
   Brainstorming terkait fitur ini memiliki dua kegiatan utama,

2. Memutuskan fitur-fitur yang tidak dibutuhkan,

3. Menggabungkan fitur-fitur yang bisa digabungkan.

4. Cari feedback
   Setelah memutuskan fitur apa yang akan dikurangi dan digabung, kembali turun ke lapangan untuk mendapat feedback. Apakah MVP dengan fitur-fitur yang ditetapkan tadi dapat menyelesaikan permasalahan?

5. Hitung MVP Anda
   Jangan hanya mengandalkan feeling, "Sepertinya ini sudah minimalis. Maka produk ini sudah benar". Penghitungan MVP dapat dilakukan berdasarkan feedback-feedback yang telah kita dapatkan sebelumnya dari pengguna.

Viability juga perlu diperhatikan pada bidang apa Anda mengembangkan produk Anda. Setiap bidang akan memiliki tingkat viability yang berbeda. Misalnya, untuk bidang e-commerce, viability adalah jika minimal MVP Anda adalah hal yang paling sederhana, yaitu kemampuan produk Anda untuk menemukan menemukan dan membeli produk. Berbeda dengan bidang sosial, maupun marketplace.

Referensi:
https://alexiskold.net/2015/10/07/re-thinking-viability-of-your-mvp/

After making your Minimum Viable Product, what's required is to test if it is viable enough to be changed into a Minimal Loveable Product.

Following is the process (steps) to test your MVP

Step 1:

My suggestion would be to ask a few of your friends to play around with the product. Ask them to give a critical feedback. Analyse the feedback to see if their understanding of the product is the same as you intended it to be. Iterate the product based on the feedback.

Step 2:

Find a niche group of people who can dedicate a few hours to your product weekly. Ask them if the product is solving any real life problem of theirs. Ask them what would make them use your product more, and are they willing to pay for it (depending on your business model). Based on their feedback, iterate your product.

If you are unable to find a niche group of users, hire some interns, pay them a little stipend, and ask them to use your product. Observe their behaviour, and analyse how they use your product.

Step 3:

Use websites (like usertesting dot com) to get authentic feedback from real users who don’t know you personally. Iterate over the feedback. And then launch your product on beta testing websites like Product Hunt to get initial set of users.

How to measure MVP success:

1.Communication comes first

If you want your software to be popular and you don't want to repel users, start communication with potential customers. Promote your product on different forums, speak with visitors, ask them for feedback, let them share their opinion and tell you about any problems that your software has.

2. User engagement

Measuring user engagement, you will be able to see how your product is valuable for today, and even evaluate the potential of your software, how it can be popular in the future. With the help of user engagement metric, you will be able to modify UX if necessary.

3. The number of downloads

This metrics is important if you create an MVP of a mobile app. The more downloads and launch rates your app has, the more popular it is, the principle is simple. That is why in the case with an app you should always monitor this metric.

4. Percentage of active users

If your app has 1000 users, it doesn't mean that all of them actively use this app. Therefore, you should check it out how many users are active and think through a strategy to retain passive users and make them return to your app. So monitor this metric regularly.

5. Percentage of paying users

If you earn on your software, you should know how many users are using paid services in your software, find more information about users, why they are interested in your software, what they like, how much time they used your software before they start using paid services and so on. Keep it in mind that the number of paying users will always be less than the number of free users.

6. Customer lifetime value

This metric is also crucial, it gives you an understanding of how long users spend in your software before they remove it. If this time too short, you should monitor other metrics to find out the reason for such activity.