Pod Insights The Agile Daily Standup - AgileDad MVP is Dead!! We Should Focus on MLP Instead! About this episode MVP is Dead!! We Should Focus on MLP Instead! MVPs sound great in theory, but too often, they result in forgettable, uninspiring products. Instead of focusing on minimum viability, focus on minimum loveability – because a product that people love will always win. So, the next time someone tells you to build an MVP, ask them:“Would you rather date someone who’s ‘viable’ or someone who’s lovable?”How to connect with AgileDad:- [website] https://www.agiledad.com/- [instagram] https://www.instagram.com/agile_coach/- [facebook] https://www.facebook.com/RealAgileDad/- [Linkedin] https://www.linkedin.com/in/leehenson/
Transcript 0:16 Speaker 00 One of our loyal listeners asked me to go ahead and do an evaluation of an article that was published. And I have to admit, at first, when I read through it, I got a kick out of it. And I said, I have to check the date to make sure it's not an April Fool's joke before I put it out here, even though we're listening to it here in May. So it starts off with, let's start with a reality check. How many times have you excitedly launched a minimal viable product, only to hear crickets? Or worse, your users try it once and make that disgusted face. You know, the ones like when your friends from the deep south accidentally get sugar-free tea instead of sweet tea and never ever go back? The MVP concept was introduced by Eric Ries and Lean Startup, and it was meant
1:01 Speaker 00 to be a game changer. But the smallest version of your product, you build the smallest version of your product, rather, get early feedback and iterate. It sounds great in theory, but in practice, it often results in half-baked products that nobody really likes. Let's face it, MVPs are often just bad products. Let's start, let's stop there for a moment. I think this has to do with, this is a symptom of a different problem. So for me, when I look at this, the first thing that I see is that this person is putting their toe in the water of discovery. They haven't really done initiate, they're doing discovery, but they're not doing it in the right way. So because
1:44 Speaker 00 they're still almost 98% in delivery and only 1% or 2% in discovery, they're, they're not discovering the true purpose of what an MVP is for. So let's keep going and see where they take it. Here's what usually happens with an MVP. One, it's too basic. It only does one thing and badly. Two, it's just ugly design. What's that? Nobody took the time. Three, it's confusing. The onboarding experience is only an afterthought. People don't know what to do with it. Four, it doesn't hook users. The viable part is so weak that users bounce faster than a bad date. In short, MVPs feel like someone is serving you an uncooked pizza and saying, imagine how good this will be once it's cooked.
2:30 Speaker 00 No, thanks. I'd rather not get the food poisoning. But I think that if MVPs are about viability, we need to come up with something else. And this author says we should be focusing more on minimal lovable products, MLPs, because MLPs focus on lovability. Because no one shares a product that no one shares a product that they only tolerate. So when you start asking yourself, okay, this sounds crazy because that's exactly what I did. Why is a minimal lovable product better than a minimal viable product? Factor: Minimal viable product. Minimal lovable product.
3:16 Speaker 00 Purpose: Validate idea, create emotional connection. UX/UI: Basic, often clunky, polished, delightful. Ah, I got it. So this is supposed to be like a table. With an MVP, the purpose is to validate the idea. The UI and UX is often basic. The user engagement is left at users try then leave.
3:46 Speaker 00 It's iteration based on early feedback. Okay? When you do an MLP, it creates an emotional connection. It's usually polished and delightful. Users stay and advocate for the use of Jitter product. And you get the early feedback based on user excitement. So a great example of this is Slack. When Slack first launched, it wasn't just viable, it was fun. The quirky loading messages, emojis, GIF integrations made it instantly lovable. No one begged for a competitor.
4:21 Speaker 00 Uh, you know, so here's why MVPs fail more often than they succeed. Ninety percent of startups fail. A major reason, they launch half-baked products that fail to engage users. That's true. Users form opinions in about point zero five seconds. I believe that too. If, if your MVP looks like a nineteen ninety nine website, they're done. They're gone. Retention is the key to success. If users don't love your product, they won't stick around to see what your iterative improvements will be because they don't like your original product. So how do you now go about building an MLP instead of an MVP? You start at the top by solving a pain point in a delightful way. Your product should make users say, where have you been all my life?
5:06 Speaker 00 Not, oh, great, another app I'll wind up deleting next week. Number two, don't launch ugly. An MVP with poor design is like a new restaurant with dirty dishes and tables. Users won't wait for you to get around to washing the dishes at a tablecloth. They'll go to a different restaurant. Number three, focus on the addictive hook. WhatsApp had free messaging. Instagram had filters that made everyone look like a pro. TikTok made anyone a perfect entertainer in fifteen seconds. What's your hook? And then finally, number four, prioritize the light over speed. Yeah, speed's crucial, but a delightful experience is what makes people stick around. Think of how Agile polishes its products before they launch them.
5:47 Speaker 00 MVPs sound great in theory, but too often they result in forgettable, uninspiring products. Instead of focusing on minimal viability, we should be focused on minimum lovability because a product that people love will always win every time. So the next time someone tells you to build an MVP, ask them, would you rather date someone who's viable or someone who's lovable? Oh, my goodness, that is the best closing line I've heard in a long time. I just wanted to thank you to author this article. It was pretty awesome. I think her name was Garama. Garama, thank you so much for writing that. It is a powerful article and you know what? It's true. So I want to thank you all for being here. If you have a topic you want us to discuss or an article you want me to review, feel free to reach out, learn more at agiledad.com. I'd love to hear from you.
6:31 Speaker 00 And as always, I encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care. Bye now.
Previous Remove From Your Process as Often as You Add To It - Mike Cohn Next Leadership IS Language! Page updated November 7, 2026 · transcript and summary are machine-generated