Having started my career in the heyday of Total Quality Management (it brings us back to the early 1980s!) and being educated to worship customer satisfaction in the Lean way, I am not very at ease with the Minimum Viable Product concept.
A minimum viable product has just those core features that allow the product to be deployed, and no more. The product is typically deployed to a subset of possible customers, such as early adopters that are thought to be more forgiving, more likely to give feedback, and able to grasp a product vision from an early prototype or marketing information. It is a strategy targeted at avoiding building products that customers do not want, that seeks to maximize the information learned about the customer per dollar spent. https://en.wikipedia.org/wiki/Minimum_viable_product
Even so I fully understand and partly support the strategy, I am experiencing cases that keep fueling my distrust.
>Lisez cet article en français
The one that got me angry and triggered writing this post is about an app designed to manage social media.
I have several accounts within this app and to my surprise, the app has different behaviors and proposed features, depending the account I log in with.
This inconsistency is quite a surprise and does not suggest very good standards nor consistency in development strategy.
Over time, I experienced several bugs and even gave detailed feedback to help the developers’ team to improve. But it seems that every time they fix one, a new one appears. The latest denied me programming posts at desired time, which is the very basic function this app is made for!
I am using the free version and this is supposed to be the showcase for the premium offer. I’ll never go premium and I will quit using this app.
What I supposed to be ongoing improvement on a minimum viable product is just steadily proposing new crap. Hence my reservations about the concept, which is likely to be used to camouflage poor capabilities to deliver.