Avoiding the Wrong MVP Approach

UX Strategy with Jared Spool, a Center Centre — UIE newsletter focused on bringing UX to a strategic level inside your organization.

Image for post
Image for post

What about an MVP?

The claims processing product team was chartered with figuring out how to make something like this work. In the olden days, they would just dive in and build working functionality, hoping it would work great when launched. But, it never worked great.

What exactly is an MVP?

For many organizations, they’ve come to use MVP to mean a less functional, limited implementation application. Build it quick, get it into the hands of customers, and see how they like it.

Iterate on the learning

The team started by breaking down the questions they needed to answer. The first question was, could they get customer-supplied pictures that would be good enough for the claims adjusters?

MVPs: No coding necessary

Without writing any code, the team learned what they needed: customers could supply valuable pictures. That was only the first step, but it was a big one. (Next up: could they easily get those pictures into the existing claim system?)

UX Strategy with Jared Spool

This article was originally published in our new UX Strategy with Jared Spool newsletter. If you’re passionate about driving your organization to deliver better-designed products and services, you’ll want to subscribe.

Written by

Maker of Awesomeness at @CenterCentre/@UIE. Helping designers everywhere help their organizations deliver well-designed products and services.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store