It is accepted best practice in the IT world that whenever anew product is launched, the first version to ever get in the hands of users is not the fully fledged product. Why? For two very simple reasons: it costs a lot of money and a lot of time, which can make you miss your market opportunity and put you in the red.
What users first interact with is an MVP. An MVP, or the Minimum Viable Product is that version of your product that lets users testcore features and shows that what you intend to achieve. In other words, how you intend to serve users and bring value in their lives.
Building an MVP is easier said than done. But there is astep-by-step process you can follow, to ensure you’re building the right thing,for the right people. The core action in this process is listening – listening to their problems, their needs, their current solutions and most importantly, listening to the way they feel about your product. In other words, understanding and tracking customer behavior.
Did you know that in most cases, they don’t actually buy what they say they would and end up purchasing exactly the opposite?
Yes, people are … weird. But there is something you can do about it! Below are the steps we at We As Web deem necessary in order to build and MVP:
· Visualize the ideal client persona and set thetarget market;
· Launch a smoke test to validate your business idea by building a simple landing page describing what you want to achieve with your product and see the feedback you receive
· Establish the basic product/simpler version of the product – your core features, but do not invest to much in it as this version is meant to be updated;
· Use low-code or no-code tools to create a proof of concept. Let some users see it.
· Research can help you build confidence that you are building the right thing (do industry search and run user surveys). But it can also give you a false-positive that the product you have in mind is neededin the market.
· Build the MVP version, either with your owntechnical skills or by finding a tech development partner
· Release your MVP to real users and get feedbackas soon as possible – be receptive and improve in the direction pointed by users;
· Do not get attached to how you wanted the product to be and try to be receptive on how it is received in the market
Easy right? It can be. With the right people by your side, to guide you in developing the strategy for your product and in building the features users love.