What’s worse, when your product is released, you may find that customers just don’t like it very much, so the team hopes that they can test customers more first.

More features will then be added based on customer feedback driven insight gained through the launch.

The result may be good, but it may also backfire, deviate from the original vision, or misunderstand due to lack of consultation with the product team during the long development process.

Although there will inevitably be project checkins and ongoing work demonstrations, this still exists – “Ta Da” moments and “big secrets” – the development team will publish the project output to the product team for the first time.

This is an approach we adhere to in the browser.

The development team may also encounter obstacles and problems, resulting in overspending of the project; In the worst case, all the original budgets may have been exhausted, and the key parts of the original scope have not been delivered.

Most projects follow the waterfall method (open in a new label) [en.wikipedia.org/wiki/w], which usually means that software developers will build more comprehensive solutions according to a set of detailed requirements.

Feedback, analysis and adoption of figures can reveal[ https://www.browserlondon.com/blog/2018/02/20/research-discovery-shape-ui-thinking/ ]Insights that surprise you allow you to better prioritize new features and even implement more fundamental changes that might not have been anticipated without the MVP approach..

One of the most powerful advantages of MVP is that you can take advantage of the power of real feedback from customers.

The number of users who use your site or application, how they actually use it, and how they feel about it provide the best insight into how to receive your digital output, allowing you to make the necessary adjustments[ https://www.browserlondon.com/blog/2018/12/11/continuous-development-web-design/ ]And improvement.

What is MVP? MVP represents the minimum feasible product.

Once we explain its benefits in terms of availability, adoption rate, budget and time to market, we usually find that our customers agree with us.

Fortunately, the dark days of pure waterfall method have basically ended.

Some large waterfall projects[ https://www.browserlondon.com/blog/2019/04/30/hertz-accenture-blame-game/ ]The length of may cause time problems.

running waist packs

Regardless of the detailed pre development discovery phase[ https://www.browserlondon.com/blog/2021/07/22/demystifying-the-discovery-process-our-four-stages/ ]How valuable it is that customers’ real reactions to your website, application, service or product always surpass it.

In the case of digital projects, this means that you will look at earlier versions that have been narrowed down, then push the rest of the required scope through further versions, and further understand that your website, application, service or digital product is received by real users in the real world.

Most digital projects are applying a more agile and iterative method, thus alleviating many of the above traps (sometimes this is agile with a small “a”, rather than necessarily a fully implemented agile method[ https://www.browserlondon.com/blog/2015/05/28/the-agile-process-explained-for-non-technical-people/ ]）。 Here, the MVP approach plays an important role in conjunction with other aspects, such as user centered design techniques (such as prototype design), better feedback cycles with product teams and customers, and a more user centered mindset from the development team.

(just to make things complicated, in the field of software development, it also represents Microsoft’s most valuable professional plan, and for the gamers there, it can represent the most valuable players, but this may be another article.) In short, MVP releases products in versions that have the least functionality to meet customer needs.

Establishing a minimum viable product (MVP), bringing it to market, and then building on it through a series of iterative improvements is now basically the practice when creating new digital products.

Dark days of pure waterfall in order to correctly explain the power of adopting MVP method, we need to go back to digital projects a few years ago and review the dark days of pure waterfall.

1.

Specifically, there are some real benefits to adopting the MVP approach, especially when providing insight to the team, they don’t run before they walk.

Let’s listen to MVP.

take advantage of the power of real world feedback.

Let’s look at six specific advantages of MVP.

Perhaps the opportunity has been missed, the delivered products are not as successful as they were launched six months ago, or all your competitors have arrived there first and provided their products.

In this article, we will explore what MVP is, and explore in depth the advantages this approach brings to the project.