In the late 1990s, WebVan was going to transform the grocery business through online ordering and home delivery. But just a few years after being founded (and $1 billion in infrastructure investments) the company was bankrupt.<\/p>\n\n\n\n
What happened?<\/p>\n\n\n\n
A lot of mistakes were made. The case could be made that WebVan was simply too far ahead of its time. Given the popularity of online grocery ordering, pickup and even delivery today, it seems likely that WebVan paid a penalty for being too early.<\/p>\n\n\n\n
But their biggest mistake was that they fell in love with their idea. Then they worked hard to make that idea a reality. A lot of really smart people held meetings and set budgets and timelines and executed their plans. They spent a tremendous amount of time and resources to pushing the idea forward and into the marketplace.<\/p>\n\n\n\n
But there was something they didn\u2019t do. They didn\u2019t take the time to understand the market and the customer problem they were trying to solve. They didn\u2019t test their product and validate their idea. They failed to realize that the market wasn\u2019t quite ready for online grocery shopping. They created a well-developed product that failed to create enough interest to make it commercially viable.<\/p>\n\n\n\n
Simply, they didn\u2019t find the Product\/Market Fit.<\/p>\n\n\n\n
In its time, WebVan was a cool idea. At the time, internet retailing was beginning to take shape, and WebVan wanted to do for groceries what Amazon was doing for books. It seemed like a cool idea, since people bought groceries far more frequently than books, and it had the potential to save people hours every week.<\/p>\n\n\n\n
WebVan was built on its coolness. They wanted to find out if they could build a new business model. They never asked if they should.<\/p>\n\n\n\n
When it comes down to it, people don\u2019t care about coolness. They care about their needs and their problems. If a product or a company can solve their problems in a compelling way that they\u2019re willing to pay for, that\u2019s what\u2019s cool.<\/p>\n\n\n\n
That, in essence, is what Product\/Market Fit is. Understanding the customer problem that needs to be solved, understanding the marketplace and people\u2019s willingness to pay for a solution, and testing the product to find the right approach that can then be scaled. You know when you have Product\/Market Fit when you start to see user adoption.<\/p>\n\n\n\n
It\u2019s asking, \u201cShould we built it?\u201d instead of \u201cCould we build it?\u201d<\/p>\n\n\n\n
Had WebVan determined their Product\/Market Fit before they scaled their operation with massive infrastructure investments, they would have seen their planned approach was doomed to fail. And they also might have pivoted to an approach that would have worked.<\/p>\n\n\n\n
Maybe they would have uncovered some aspect of grocery shopping that annoyed shoppers or identified a certain segment of the market that was open to their service. Then they could have built their business accordingly.<\/p>\n\n\n\n
It\u2019s easy to look at the Dark Ages of 20 years ago and marvel at how foolish we all were. But companies of today are not immune to the same mistakes WebVan made.<\/p>\n\n\n\n
The smartphone has spurred a digital revolution of which we\u2019re still only seeing the beginning. Mobile technology has made it possible for users to be able to consume media, share content, interact with others, and purchase nearly anything from a convenient, handheld device. This has given rise to companies like Uber, Airbnb, and many others who continually raise the bar for functionality and user experience.<\/p>\n\n\n\n
Entrepreneurs and Fortune 500 companies alike are bent on becoming the next Uber, disrupting industries or creating new ones. With so much energy and creativity and desire in the marketplace, and consumer expectations on the rise, there is a great deal at stake. This has made the fundamentals \u2014 Product\/Market Fit \u2014 more important than ever.<\/p>\n\n\n\n
Finding Product\/Market Fit is the process of stepping back from your idea, understanding the customer problem you\u2019re trying to solve, understanding the market\u2019s desire for a solution, and testing prototypes to validate your ideas (or invalidate them and adjusting them).<\/p>\n\n\n\n
It\u2019s simple in concept, but requires discipline. It seems counterintuitive at times, and requires a decidedly unconventional approach compared to what most executives are used to. But it\u2019s the best way to arrive at a product that is truly innovative and will be embraced by the market. If nothing else, it helps you avoid investing huge sums of money in something that will never work.<\/p>\n\n\n\n
In future articles, we\u2019ll discuss specific methods for finding your Product\/Market Fit. But here are four basic principles that can guide you as you embark on this journey:<\/p>\n\n\n\n
At Digital Scientists<\/a>, we don\u2019t trust our own ideas, nor do we trust our clients\u2019 ideas. Why? While some of us may be a good fit for the product (we love using mobile apps<\/a> as much as we love designing them), we\u2019re too close to the product and too small as a group to give an accurate representation of the market. Customers, or the market, make the decision of whether your product will appeal to a large audience. And the market is always right.<\/p>\n\n\n\n Instead of getting too enamored with your ideas, find out what the market wants. Find a problem that\u2019s not being solved in a satisfactory way. Let the market pull the product out of you, instead of pushing it out.<\/p>\n\n\n\n A key part of this is understanding the size of the market. How many people are suffering from the problem you\u2019re trying to solve. It may seem obvious, but it\u2019s a key piece of information in building a sustainable business, and it\u2019s often missed.<\/p>\n\n\n\n This requires looking at the big picture, taking several steps back and asking \u201cwhy\u201d repeatedly, until you find the root cause of the customer problem. It\u2019s not easy, and it might require some outside perspective, but it\u2019s the most important step.<\/p>\n\n\n\n Absent a clear understanding of Product\/Market Fit, companies \u2014 from the largest corporations to mom & pops \u2014 will go to a designer and ask for a web site or an application. The project will get whittled down based on what functions are possible in the given time and budget.<\/p>\n\n\n\n Eventually, the application will be built, on time and on budget, and it will be deemed a success. And it will still fail. This is what happened at WebVan, on a massive, billion-dollar scale. These conventions companies follow, of setting timelines and budgets and execution plans, present artificial constraints, and they have no place in the process of innovation.<\/p>\n\n\n\n It seems counterintuitive, but the process of finding the Product\/Market Fit may require you to go over budget and past your timeline. It\u2019s an iterative process characterized by creating, testing ideas, validating (or invalidating), learning, adjusting, and repeating.<\/p>\n\n\n\n That\u2019s because you never know what the market will tell you. It might be trying to pull a product out of you that you never imagined. Putting a timeline on it will most likely cut it short before you arrive at the solution.<\/p>\n\n\n\n While the thought of going over budget may seem frightening, remember that it will still be a fraction of going all in to launch a product that\u2019s fully developed, but not the right fit for the market.<\/p>\n\n\n\n The\u00a0Minimum Viable Product, or MVP, is one of the best ways to develop and launch a prototype and find the Product\/Market Fit. It involves creating a product in fairly rapid fashion, complete with bugs, glitches and other problems, and unleashing it on a test market to see if it works.<\/p>\n\n\n\n That\u2019s another frightening thing for many entrepreneurs and executives: the idea of putting out a product that doesn\u2019t have all of the features and functions that were initially envisioned. But what the MVP does is gets the product in the hands of potential customers quickly. That, in turn, leads to faster feedback and allows you to make adjustments quickly, and based on real-user information.<\/p>\n\n\n\n That will give you the proof you need to determine what features users truly want and will use, and move on to the next phase of development.<\/p>\n\n\n\n Once you have proof that the product will work and understand how the market wants it. Then your job is to execute \u2014 build, scale, market your product.<\/p>\n\n\n\n You can proceed with confidence, because by determining your Product\/Market Fit, you know what your growth engine will be. You know who your customers are, what\u2019s important to them, and how they are going to use your product.<\/p>\n\n\n\n You know this because you will have tested and adjusted, tested and adjusted, pivoted, adjusted, and tested again. You\u2019ll know that you can and should continue to develop the product.<\/p>\n\n\n\n Or, you may not. You may not find the Product\/Market Fit. The market may keep telling you, no matter what changes you make, that it doesn\u2019t want that product. Certainly, that\u2019s not what you want to hear, but it\u2019s better than hearing the voice of a bankruptcy lawyer.<\/p>\n\n\n\n There are no guarantees, of course, but knowing you have found the Product\/Market Fit gives you confidence. Confidence that you have the basis for a product that people will use and can be scaled, possibly to become a stand-alone business. Confidence from knowing your product enhances people\u2019s lives through simplification, enjoyment, utility or purpose.<\/p>\n\n\n\n Confidence comes from knowing you aren\u2019t pursuing an untested idea because the market told you it delivers real value.<\/p>\n","protected":false},"excerpt":{"rendered":" WebVan went bankrupt because they didn\u2019t understand the customer problem they were solving. Consumers care about their needs, their problems, and solutions.<\/p>\n","protected":false},"author":1,"featured_media":4097,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"om_disable_all_campaigns":false,"inline_featured_image":false,"_price":"","_stock":"","_tribe_ticket_header":"","_tribe_default_ticket_provider":"","_tribe_ticket_capacity":"0","_ticket_start_date":"","_ticket_end_date":"","_tribe_ticket_show_description":"","_tribe_ticket_show_not_going":false,"_tribe_ticket_use_global_stock":"","_tribe_ticket_global_stock_level":"","_global_stock_mode":"","_global_stock_cap":"","_tribe_rsvp_for_event":"","_tribe_ticket_going_count":"","_tribe_ticket_not_going_count":"","_tribe_tickets_list":"[]","_tribe_ticket_has_attendee_info_fields":false,"footnotes":""},"categories":[42,43],"tags":[],"coauthors":[35],"class_list":["post-2590","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-archived","category-product"],"acf":[],"yoast_head":"\nValidate, learn, repeat<\/h4>\n\n\n\n
Launch and test an MVP<\/h4>\n\n\n\n
Build, execute, scale\u2026or abandon<\/h4>\n\n\n\n