As a contractor or end-point service company, you may not build a ton of products, but you probably create new processes all the time. I was fascinated to learn that the MVP (minimum viable product) concept applies not only to making products, but to creating processes. Let’s take a closer look at this concept.
According to aby SSC Associates, the typical failure rate for new services or products offered by companies is approximately 40 percent.*
*Many articles report figures as high as 80 to 90 percent. The SSC study reviewed many research reports and proved that in reality, between a third and a half of all new products fail.
This rate includes both products that are cancelled in development and those taken off the market after release. Products or service offerings that fail after release can cost a company a lot more than those killed because issues are uncovered during the development process.
The following lists the costs associated with each:
Table of Contents
- 0.1 Cancelled in Development
- 0.2 Fail After Release
- 0.3 Product or service developers fail to do things like:
- 1 Case Study:
Cancelled in Development
- Product or service development
- Research and testing
- Product models and prototypes
Fail After Release
- Product or service development
- Research and testing
- Product models and prototypes
- Training and related materials
- Marketing and advertising
According to information published in The Harvard Business Review, the most common reasons for products or services failing after release tie to a single issue: a lack of research.
Product or service developers fail to do things like:
- Test the product or service to make sure its differences will attract buyers
- Check that consumers can understand its benefits
- Find out who will buy the product or service and how much they’re willing to pay for it
- Ensure that everything is ready for launch.
History is chock-full of new product failures that can be tracked back to a lack of consumer knowledge, insights and research. See how many of these you remember:
All product or service failures don’t come from big global corporations.
I recently spoke to Brandon, who runs a company that leases out electronic equipment to nightclubs and other music and entertainment venues. He had a big idea for a lighting system that would automatically respond to a band’s music without a person running it. He believed it would cut lighting costs for smaller bands and venues while still providing a high-end lighting experience.
Brandon spent a significant amount of time and money designing, building and launching his product. Within a few weeks of product release, he found that most bands were uncomfortable with it. They thought it was distracting compared to the typical lighting systems run by people that they were used to. Over time, he found no one was interested in leasing his innovative system and all the time and money he spent on it were completely wasted.
Today, Brandon admits that it would have made sense to test his idea with some bands and nightclubs during the development process. It would have given him a chance to cut his losses sooner or change the product so the bands would have been more comfortable with it.
Why do so many products and services get released without testing?
Because many developers believe they can only begin testing when they have a completely finished product prototype or service offering. And once they’re at that point in the development process, they have so much invested that they just push ahead and release it to the public without testing.
The Solution: Minimum Viable Product
The concept of minimum viable product lets you test a product throughout the whole product development process. That’s because you don’t need a finished product or prototype to do so. The same concept can be applied to a service offering.
A minimum viable product (MVP) is one that has been developed with enough features to test it with consumers, gather insights on it and and make decisions about its continued development. You simply take your product to the level needed to be able to test it with consumers at different points in the development process in a wide range of research channels. And if you’re creating a service, you only develop the offering to the point where you can test it.
Depending on the type of research you’re doing, and where you are in the development cycle, you could test your product using a:
- Product description and / or illustration
- Simple model
- Prototype with limited functionality
- Completed product prototype
There are two clear benefits to the minimum viable product approach:
- You only spend enough develop your product to the level of completion needed to test it.
- You can stop and test your product at any point in the development process whenever you have questions about it.
There are countless ways you can test an electronic product. And these ideas can be applied to service offerings, as well. They include:
|Testing option||Description||Minimum Viable Product Requirements||Plusses||Minuses|
|Consumer panel discussion||Invite a group of current customers or people similar to them to get together to discuss your product idea.||Clear description of the product, rationale for developing it, and (possibly) an illustration showing features.||Easy and inexpensive way to get an early read on a product idea. A discussion with current customers during the ideation phase could help you decide whether it’s worthwhile to move ahead with the concept.||Not scientific research. Simply directional indication of whether your idea is a good or bad one.|
|Online survey||Develop an online survey that asks your customers or people similar to them questions about your product concept.||Clear description of the product, rationale for developing it, and (possibly) an illustration showing features.||Easy and inexpensive way to get an early read on your product idea. If you use a professional to develop the survey and to find the right people to complete it, you might get sound statistical data.||If you create the survey yourself, it will likely not be statistically sound, but could provide direction on whether to move ahead with your product idea or to abandon it.|
|Focus group||A research company invites a group of people similar to your customers to have an unbiased discussion about your product and to review it. A focus group can be conducted in-person or online.||Focus groups tend to be used relatively early in the product development process. You may only need a product description and illustration or a simple non-functioning product model.||Focus groups will get you a lot of impartial subjective information. People are more likely to speak-up and express their opinions when they have no direct association with the firm developing the product and the inventor is not present in the room.||The information from a focus group can be helpful, but you have to remember that it is subjective and gathered from a limited number of people.|
|Lab testing||People who are similar to your customers do hands-on testing of your product in a lab setting.||You’ll need a product prototype with enough functionality to do “hands-on” testing of the product features you want to learn about.||Lab testing is where you’ll start to find out whether your product is a winner or not. Hands-on interaction let’s you see how your product functions when people who are similar to your customers use it.||You may not get a complete picture of how effective your product is because you could be testing one with limited features in an artificial environment.|
|On-site testing||You take a product that is close to completion and test it in real-world situations.||Once you’re testing in a business, you should be using a close-to-finished product sample. Create a full-feature prototype that is durable enough to survive testing in an actual workplace.||You will see how your product functions — and integrates into the legacy systems — of actual workplaces. This is real-world testing that will get you real-world insights about your product.||Don’t get complacent about results this late in the testing cycle. If you uncover issues during onsite testing, you should fix them and do more on-site testing with a new prototype. Ignoring issues now could be as devastating to your product launch as having never done any testing at all.|
A disciplined approach to testing
You may — and probably should — use all these testing options as part of your product development process. The same is true for new services. Here’s what a sound testing plan could look like (you’ll want to develop a custom plan designed aligned with the development of your electronic product):
How testing can pay off
A benchmarking study by The Product Development Institute (PDI) and APQI reveals that organizations that take a more disciplined, research-based approach to product or service development have greater success and lower failure rates when they release them to consumers.
This chart shows that the top performing development companies have a 62 percent success rate in new launches. Their middle-performing competitors have an almost 50/50 rate and undisciplined bottom performers have just under half their offerings succeed.
Looking at this in another way, top-performing companies that do more research are more likely to kill or cancel concepts in development, limiting the dollars they waste on things that won’t make it in the marketplace. And in the end, a research-based approach limits the number of products or services that they release to consumers that fail to just 14 percent.
Note: There is one other important reason why you want to avoid releasing products or services to consumers that they don’t like. It could tarnish the image of your company and prevent them from trying out other things you recommend. It can be almost impossible to regain consumer trust once it’s broken.
Brandon, the guy who had the lighting-system product failure, admits that he has implemented a testing plan for the development of his next electronic invention: an inexpensive, high quality sound system for smaller concert venues.
He plans to use the minimum viable product approach because this will be a costly product to develop and he doesn’t want to waste money on another dud. He plans to start by testing concepts and plans in the early part of the research cycle, moving to a limited-feature prototype in later research, then an actual, full-feature product prior to release. He even has money set aside to sponsor a night at a club so he can try it out in a full venue.
Like Brandon, testing should be an integral part of your electronic product or service development process. The minimum viable product approach could be the solution you need to keep your research costs low while still getting the consumer insights you need. It can be a great way to avoid failures that could cost you a lot financially, and to your company’s reputation.