Why Social Impact Organisations Should Reconsider Minimum Viable Products in the Agile Process

With digital becoming increasingly mainstream in the social impact sector, more organisations are practising Agile - the way of working used to create and maintain most digital things and all the platforms we interact with everyday. Agile is a digital creation process that strives to launch features little and often, getting a product into the user’s hands as quickly as possible, and using feedback to determine what features to add next. It’s a process used by many of the digital products we use regularly - like Facebook and Google.

Agile is a brilliant, collaborative way of working that places users at the heart of the production process, which is exactly where they need to be. However, when creating digital products for hard-to-reach users, some parts of the Agile process require modification such as how and how often feedback is gained, the frequency of product updates and the role of the MVP.

In this blog post, we’d like to focus on the MVP portion.

An MVP (minimum viable product) is a version of a digital product with just enough features to be functional for early users, who will then later provide feedback for future iterations and improvements.

Eric Ries, who popularised the concept of MVP in 2011 in his book The Lean Startup, states that the MVP's sole objective is not to create a good user experience, but instead to generate learning:

As you consider building your own minimum viable product, let this simple rule suffice: remove any feature, process, or effort that does not contribute directly to the learning you seek.

MVPs work really well when there is both an easy, frequent feedback loop and digitally literate users who have well-managed expectations of an MVP’s purpose.

But hard-to-reach, digitally illiterate users in low internet resilient environments often don’t fit that criteria. AND they usually don’t have the time needed.

When the MVP is deployed to excluded, hard-to-reach users, it can take time to download, use, and then give feedback on it. The MVP - which by its nature comprises a small feature set focused on functionality, over usability - often does not meet enough of the user's needs to be perceived as useful or better than their existing way.

As a result, the user often has an unfulfilling first experience with the product and reverts back to their previous familiar method. The next time feedback is needed, users are (understandably) reluctant to donate their time to a product they don’t believe adds value to their life. Especially one they stopped using after the first unsuccessful experience.

The critical ongoing feedback loop needed for Agile development can’t be initiated.

Unless we have real, easy rapid feedback loops with users who understand what an MVP is, are digitally literate, and time-rich, we should stop creating MVPs in their current form.

What should we be doing instead?

At Here I Am, we create Minimum Valuable Products.

A Minimum Valuable Product is an extension of the original MVP concept. Rather than looking to create the minimum viable iteration of a product, we create the minimum iteration of a product that is capable of providing meaningful and lasting value to our users’ lives.

Unlike MVPs which often feel incomplete, Minimum Valuable Products are simple, but complete. They are ideal for including hard-to-reach, digitally illiterate users and provide a better user experience. Google Docs is a great example of this. It launched with only 3% of Microsoft Word’s features, but it still felt useful and most importantly better.

Creating a Minimum Valuable Product instead of a Minimum Viable Product increases the propensity for users to adopt the product into their lives from the get-go. Once they begin using the product, you can open up a feedback loop with the user based on their ongoing experiences using the product. And so a meaningful Agile journey that immediately adds value to both the user and the product begins.

MVPs aren’t the only area we urge you to reconsider when adapting Agile for hard-to-reach users - we share our thoughts on how to construct a respectful feedback loop here.

Minimum Valuable Products have another appealing benefit for social impact orgs: they aren’t dependent on further investment in order to add value. It’s always better that version 1 of a digital product evolves, but you also have the option of not immediately investing more into the product while still adding value for users. An MVP without additional investment is just a bad product. A Minimum Valuable Product without additional investment is a good, if modest, product that most importantly adds value to its users' lives.

If you would like to chat more about Minimum Valuable Products, or creating digital products for excluded communities, we would love to hear from you! Join the conversation on LinkedIn.

Inspired by this post?

We love to share perspectives, thoughts and ideas on creating digital ways to include the excluded. If you have a problem you'd like to discuss, we'd love to hear from you.