Member-only story
A Guide for Building, Launching, and Learning From a Minimum Viable Product
All the actionable stuff I wish I had known earlier in my career
Updated 4/11/2022
Since the beginning of 2019, I’ve written several posts about the concept of Minimum Viable Product, everything from what an MVP is for and how to do it to what you can expect to learn from it.
The lessons in these posts are taken from my own experience as a full-time entrepreneur over the last 20+ years, plus several advisory positions I’ve held, as well as time spent on the phone and over email answering questions from dozens of entrepreneurs who have reached out to me.
It’s my hope that others can learn from the mistakes I’ve made and seen, as well as the wins. So here they are, in order of when they should happen in the MVP process.
The Myth of Minimum Viable Product
What It’s About: This is a primer on the purpose and the misconceptions of an MVP.
Focus: Splitting out the core of the MVP — those components of the product that are meant to be tested for viability — from the infrastructure around the MVP — what makes up how it’s offered, delivered, and supported.
Action: The core of the MVP must be robust. The infrastructure is what should be minimized, and it must also be flexible, so that those aspects can be changed on the fly to test different theories.
Read: The Myth of Minimum Viable Product
This Is Why Your Customers Hate Your Minimum Viable Product
What It’s About: Before you get going, let’s avoid all the mistakes that might…
