
I don’t think I heard the term “MVP” used in software development until six or seven years ago. It doesn’t mean “Most Valuable Player,” nor does it mean either of the two rude but hilarious things from the “roasting” episode of Arliss, neither of which would be appropriate for a family website like TTAC. Rather, it means “Minimum Viable Product.”
The purpose of an MVP is to get your software out there in public usage so you can both obtain user feedback for future development and earn enough money to fund that future development. Google is well known for doing this: its original search page was the very definition of MVP compared to the monstrous multi-purpose interface that it is today.
You can make the argument that some non-software products out there are also MVPs. The toothbrush and toothpaste you get at a Holiday Inn Express when you’ve forgotten your own Black Series electric? That’s definitely a minimum viable product. When most young people furnish their first dorm room or apartment, they are definitely looking for their own MVP. When you’re traveling for business and they call closing time at the bar, you’re going to take a very open-minded view of what constitutes that minimum viable product for the evening.
What about cars? What’s the MVP of the modern automobile? Contrary to what some of the B&B believe, it’s not a 200,000-mile Corolla or Volvo. I’ve said it before and I’ll say it again: you gotta be rich to own a cheap car. Let’s look instead at what the minimum viable product might be for someone with very limited mechanical knowledge. Someone with no tools, no covered parking, no garage in which to service, no high-school buddy who now owns an import repair shop. In other words, a reliable vehicle with low cost of entry, low cost of operation, and a high likelihood of starting and running at all times.
What would that look like? What would it cost?
Read More >
Recent Comments