MVP: Sometimes Viability is Enough
In the early days of software development, big projects were usually late, over-budget and short on functionality. It was difficult because everything had to be hand-coded and written from scratch. As these behemoths limped into production, we called the result "Phase 1" - with the implied promise that there would someday be a "Phase 2" to make up for the shortcomings. "Phase 2" rarely came.
Now, with vastly improved tools and frameworks, the "Phased Approach" has been replaced by the concept of Minimum Viable Product (MVP). MVP means building the smallest possible solution that can accomplish the primary function that is required. No frills. MVP is a big improvement over the Phased Approach. It gets products to market faster and cheaper. And while both methods will launch a product without full functionality, MVP has the advantage that the missing features are carefully selected to ensure that the product can fulfill its mission. It is "viable".
The exciting thing about MVP is that the model is not limited to software engineering. It can be applied to all kinds of endeavours including marketing campaigns, product development and even companies. It simply means starting with the smallest, simplest model that gets the primary job done. The picture shows how I used MVP on an engineering project - building a bridge across the creek. My "bridge" has 5 key characteristics of an MVP:
1. It was developed and deployed rapidly (about 10 seconds)
2. It was inexpensive and therefore disposable
3. It satisfies the primary function required (gets you across the creek)
4. It is intentionally missing secondary requirements (a railing might be nice)
5. It works and does not break
By taking the MVP approach to my bridge, I will be able "market test" it. If no one uses it, maybe it's in the wrong place. Maybe we don't need a bridge.
The success of MVP in software engineering and business is self-evident. But I see it as more than just a methodology. It is a world-view of experimentation and even minimalism. As we organize our lives, our careers, our education, our style of living, would we benefit from considering the smaller, simpler, quicker solutions that get the job done without the "bells and whistles"? Is there something to be said for putting the MVP in place and just leaving it at that? Sometimes in life you will need to design and build a fancy bridge, but there will be times when it's better to kick a log across the creek, call it a "bridge" and be done with it.
I think that log will still be there 20 years from now.
Thanks Jack. I'm passing this post along. I appreciated the stretch to apply to so many aspects of life. Made me think of this one: could be too much of a stretch. It's a bit personal so easy on the followups. I started a faith journey with Jesus many years ago. You made me reflect that it really began as an MVP. Yet over the years, seeing the value of the simple beginning, I'd say my relationship with him has grown to being the main bridge to living a full life.
Love your article Jack. You can also subtitle this "How companies can avoid getting Uber-ed" or "How to come up with the next big thing" . Take new ideas, vet them, goto market fast with an MVP, then get surprised. Can't wait for your book to come out (hint- you should write one) and go out on a speaking tour. I'll be your speaking groupie :-).
Very well thought out post! I love the log over creek analogy as to me it also invokes the typical pitfal of this methodology. Security is not included in "minimum" requirement. The rail should be part of the minimum viable product. The log is indeed viable for personal use but as a service provided it leaves the users at risks of fall and injuries. Which could also leave you liable to lawsuits. So like the rail, security should never be an optional "nice to have" feature when exposed to your customers/users.
Good article. The point about market testing is an important one. Often, requirements that are considered mandatory or very important in the early stages become unimportant when the person for who the bridge was built actually uses the MVP bridge. A reassessment of what's important and what is not usually occurs after they cross the creek for the first time.
Well said Jack, for a change the MVP the example is not a mona lisa painting or a bycicle becoming a car. the example of the log really speaks for itself. Now to see how people adapt to an MVP world as even nowadays , it's hard for most of the people to understand and accept the concept of an MVP. that all possible features won't be included before going live with a product .. but rather test the market and react to it quickly.