SLC vs. MVP: What’s the difference, and which is best for your software project?
Your new custom software is going to be amazing - and you can’t wait to use it in your business. But you know that high quality software doesn’t just materialize overnight, and you want to make sure it gets built right. Which project methodology is going to get you the results you want, in the most efficient and effective way?
Perhaps you’ve heard of new software being introduced as a Minimum Viable Product (MVP). But what does this actually mean, and is it a good idea? The MVP concept became popular after the 2011 publication of startup founder Eric Ries’s book The Lean Startup, in which Ries purports that launching an MVP prior to building a full-fledged product can minimize risks.
Though Ries’s points may be valid, the MVP methodology also has some inherent flaws and isn’t the only option for getting a product to market quickly. Attempts to address MVP shortcomings and shifting philosophies eventually gave rise to the Simple, Lovable and Complete (SLC) methodology as a promising alternative.
So what’s the difference between a Minimum Viable Product and a Simple, Lovable and Complete Product - and how can you decide which is right for you?
Benefits of building an MVP
Minimum
Because an MVP is designed to be the smallest possible iteration of a software product, it is inexpensive to create. It can be built and tested quickly and easily, and brought to the market with maximum speed.
Viable
An MVP is built with just enough features to accomplish a basic task or function. It provides a viable solution to a problem, yet also incurs minimal losses if it’s not a hit with the target market, since few resources are used in its creation.
Product
Though it’s minimal, an MVP is still a real product rolled out to real users. This methodology allows the software team to get quick feedback from actual customers and learn as they go, continuing to build out the application if it seems to be a success.
Drawbacks of building an MVP
Minimum
One common criticism of MVPs is that they’re often so minimal it’s questionable if they can actually be considered a complete product. There is usually little or no consideration of what the customer considers complete, which dangerously discounts the fact that no one wants to use a mediocre product. Furthermore, pressure to do the least possible amount of work prior to launching the application disincentivizes quality.
Viable
When it comes down to the bottom line, many MVPs aren’t actually all that viable. They are designed for a quick release, not for functional efficiency or user experience. Working “just ok enough” is not the same as working great, and customers are savvy enough to tell the difference. If better alternatives exist, it’s a safe bet many will flock to them.
Product
While software teams may enjoy controlling what goes into their MVP, it’s highly risky not to have the customer define acceptable functionality from the outset. Not only is an uninspiring product likely to lose much of its user base, complaints from dissatisfied customers can negatively affect a company’s reputation. MVPs also have a low barrier to imitation and can easily be outshone by superior products.
Why consider building SLC instead
Simple
When you build a Simple, Lovable and Complete product the focus is on creating a simple application that does its job very well, not a minimal one that just does ok. This applies to both the functionality of the product and the UX design. Most customers don’t need lots of bells and whistles - but they do want a great user experience.
Lovable
Because SLC products are designed with the customers emotions in mind, people actually enjoy using them right from the start. The product provides real value, not just minimum viability. If done well, it will even surprise and delight. This makes it much easier for customers to develop a genuine affinity for the new product, which can also extend to brand loyalty toward the company.
Complete
Though it may be small at first, an SLC application is still built to be a complete product. Customer needs are thoroughly understood and optimized for right from the start, and the product is designed to provide the most important functionality, not just the most basic. Genuine value is created without any further development.
Interested in building an SLC product?
At Basecode, we don’t settle for building MVPs. They’re usually too M to be V. We use the Simple, Lovable, and Complete heuristics to build rock-solid iterations of products that deliver clear value as early as the 0.1 version. Find out more about our philosophy.