When is an MVP too MVP?

So, recently I’ve been diving heavily in how to build and manage / run a startup (primarily as its something I’m going to be doing with quickfire).

One of the key points raised in everything is build an MVP, ship it, and iterate on it. For the uninitiated, MVP stands for Minimum Viable Product. It basically means the most bare version you can get away with calling a product so that you can quickly take on feedback from users and build / change what is needed.

This methodology is what has allowed many of the largest online services launched recently to get to where they are. Instagram, Snapchat, Uber all launched as MVP and built on top of that using feedback. It works… mostly.

You see, because of it being very unique to each business, there is no defined meaning of MVP. This leads to a situation where some MVPs are possibly a bit too minimum.

Take for example, Monzo. Monzo are a new app-only bank in the UK. I’m an investor from crowdcube and an early beta user. I’ve generally been quite happy with my experience but honestly they’ve started to disappoint me.

A few months ago they made Joint Accounts available to their customers. Great! They thought. Only to be disappointed when some very key features such as Pots weren’t – and still aren’t – available for joint accounts. This is exactly what I mean by “too minimum”. Pots are a flagship feature of the primary product but were left absent in the Joint Accounts release.

But then there comes the situation of leaving features in MVP status for too long. Another example, nicely provided by Monzo, is once again Joint Accounts. You see, they were made available a long time ago. The problem? They haven’t been iterated on. The request to make Pots available is one that fills the forum and twitter, but one that has not yet made it in to the app.

This is exactly what I mean. It goes against the MVP mantra, but still happens. I want to be clear, I love Monzo and what they are trying to achieve, it is just unfortunate that they are really becoming quite disappointing and development has slowed. Dramatically.

I know I got on a bit of a tangent there about Monzo, but its an important one that I’ll leave in the post. MVP done wrong can severely impact a user’s experience of your product. Most of us will happily let you get away with MVP as long as you remember the iteration and building part. Ignore that? Well all you have is disappointed users ready to jump ship to the next startup that comes along and does develop.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.