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:
It was developed and deployed rapidly (about 10 seconds)
It was inexpensive and therefore disposable
It satisfies the primary function required (gets you across the creek)
It is intentionally missing secondary requirements (a railing might be nice)
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.