Working as a consultant, I’m always pushing for an MVP. Why? Because they’re cheaper to build, and more importantly, most people don’t actually know what to build—and they shouldn’t. Not until real users are using it, and you can clearly see and hear the value your product delivers.
So, let’s chat about an MVP—a minimum viable product.
An MVP should be three things:
- The least amount of features needed to get the job done.
- A journey that people can complete without so much frustration they give up.
- Something that adds real value.
The IKEA Bed Analogy
Let’s say you need a bed. If I ship you an IKEA MALM bed frame with no instructions, could you build it and have a comfy place to sleep? Sure—but with a lot of anguish. That version checks boxes one and three: it’s minimal, and it provides value in the end. But it fails box two. If people give up because the journey is too hard, it’s not an MVP—it’s just an MP.
Now, add some instructions. Suddenly, the same bed is achievable. The journey isn’t perfect, but it’s good enough. And that’s what makes it viable.
How to Test if It’s an MVP
One simple way: run a usability test. Give a user a goal and watch what happens. If they get stuck saying, “I don’t know what to do now”—and they can’t figure it out within a reasonable effort—you’ve got a problem.
MVPs don’t need to be perfect, but they need to be good enough: clear, smooth, and usable, so that people can actually achieve their immediate goals and see the value.
The Real Lesson
Next time you’re building an MVP, don’t focus on how awesome it is. Focus on how clear it is. Because clarity is what makes something viable.