An MVP Isn't a Crappy, Bare-Bones Product
Eric corrects the most common misconception about the MVP: that it means a stripped-down, low-quality thing that will crash your computer. He argues the MVP is simply the most efficient way to test whether your hypothesis is true — quality is defined by the customer, and if you don't know who the customer is, you don't even know what 'quality' means.
- MVP is not a specific tactic or a bare-bones build — it's whatever most efficiently validates the hypothesis
- In genuinely high-stakes industries (jet engines, data centers, oil drilling) the bar is far higher than iOS apps, yet MVP logic still applies
- If the quality bar is truly high, you can only afford one critical feature at that level — then test it
- Quality is defined by the customer; without knowing the customer, 'quality' is meaningless
- Building a high-quality product on the wrong value prop is nothing to be proud of
“people think that mvp is about a specific tactic so like an MVP is like a bare bone stripped down thing that will crash your…”
“quality is defined by the customer and if we don't know who our customer is we literally don't know what the word quality means”