In a great post Eric Ries proposes that some of the characteristics that make entrepreneurs take risks makes them especially vulnerable to making bad product decisions . Specifically, he states:
The difficulty lies in this paradox: many of the attributes that increase the likelihood of becoming an entrepreneur actually impede startup success ...It is in the psychological factors that we find the most paradox. For example, consider the propensity for risk-taking. Research has demonstrated the obvious: that people who have greater tolerance for risk or ambiguity are more likely to attempt entrepreneurship. That’s not too surprising. But does a risk-taking attitude actually lead to more startup success? The studies that have looked at this question in particular have found a negative correlation between risk-taking behavior and startup success.
That doesn’t strike me as shocking. And, although this hasn’t been subjected to a great deal of study (yet), I believe this same pattern will be found in a variety of other entrepreneurial characteristics: overconfidence, determination to succeed, perseverance, and even the desire to be in control. All of these factors are helpful in getting people to take the plunge, but all of them cause serious impairment of decision-making down the road. Think of the startups you know who are caught in a reality distortion field, heading full-speed off a cliff. Most likely, you will find the above attributes in excess supply.
Eric's "reality distortion field" is very real when launching a new product or business. You're completely excited about the idea - only the data that supports your product/business concept gets noticed. The data that doesn't support your idea gets lost. This confirmation bias is a problem for a lot of new companies and new products. Eventually, if your initial idea isn't the right one, the reality of the situation will make itself known - usually when you cannot sell the thing you've just built. Hopefully this won't be before you've spent too much money or run out of cash.
The antidote is and institutionalized empiricism that requires you to test your ideas.
At Return Path we've borrowed heavily from Steve Blank's Four Steps to the Epiphany, the excellent Entrepreneur's Guide to Customer Development and Randy Komisar and John Mullins' Getting to Plan B. One of the common themes across these three books is that your initial idea has a significant probability of being wrong. Your job as an entrepreneur is to find the least expensive and least labor intensive way to test your assumptions. There are going to be a few "Leap of Faith Assumptions" (Mullins/Komisar) that are make or break assumptions that you need to test.
So how do we do it at Return Path? We haven't completely codified how we develop new products, but typically a new product project will contain:
-
A very detailed hypothesis document - We've taken a lot of the contents of the hypothesis document from the Four Steps to the Epiphany. The document covers the customer, the problem and the solution. Because in our world, a lot of the risk is in market acceptance, we focus a lot of the assumptions about how we're going to market, sell and service the product. Ideally, this document is worked on by the product management, sales, marketing, channel and product development teams. It becomes the basis for conversation around the product and go to market strategy. During those conversations, you will unearth some key assumptions that must be closely tested.
-
A "dashboard" that focuses our attention on testing the key assumptions - We pull some of the key assumptions out of hypothesis document that are absolutely critical for the success of the project and define a test for each assumption. For example, let's say that a key assumption is that we're going to generation a certain number of marketing qualified leads over the course of a month. To test this hypothesis we will generate a lead generation program that might lead a customer to download a whitepaper around the problem that our product addresses. This is a form of "dry testing" that allows us to get a feel for whether we can create marketing qualified leads without having to develop a full product. Remember the goal is to test hypotheses at the lowest cost.
There's a lot more to applying the customer development philosophy that is well described in the books listed above. However, for me, one of the most important elements is the institutionalized empiricism that a well run customer development process can provide.