Listened to Eric Ries’ e-Corner Talk – Guess It’s Time to Pivot
A few months ago, Eric Ries gave a talk as part of Stanford’s e-corner series (“e” stands for entrepreneur). I remember listening to the first part of his talk, but for some reason I never finished it. I finally ran across it again, so I decided to listen to the whole thing. I’m glad I did.
He described a whole range of lessons learned from the various startups he’s been part of (in fact his blog is called Lessons Learned). One lesson that I found particularly relevant to me was that all successful startups “pivot”. When a startup introduces a product to a set of potential customers, they usually learn that some of their assumptions about the market were wrong. Customers will let the founders know this by saying things along the lines of “Well this is an interesting product, but what would be really useful would be X”. This feature may only be tangentially relevant to your current product. However, if several people ask for X, there might be something there. A pivot is re-orienting your product so it can do X or building a new product that does X in a viable way. You keep one foot in your current product and “pivot” to place your other foot in the new product. If you make a series of pivots based on customer feedback, you will home in on what your customers will buy.
While this sounds easy, it’s actually very hard, in practice, for an entrepreneur to do. After all, you’ve spent a lot of time thinking about a problem and building a solution to it. When you hear someone say your product is “interesting” and ask for X, your first reaction is to dismiss this idea out of hand. You may be right; you may be wrong. It’s hard to tell. Maybe your product is too far ahead of the market (e.g., WebTV, Newton). Maybe you’ve created a disruptive technology that has to find its niche first (e.g., 2.5″ hard drives in laptops). In any case, when several people ask for X after you’ve shown them your product, perhaps it’s time to listen.
Time for Lakeway to Pivot
For the past few years, we’ve been driving very hard at developing Frontier. It’s a beautiful application that addresses key management problems that, before Frontier, have defied solution. However, for the past two years, whenever I show Frontier to engineering executives, they always seem to ask for X. After listening to Eric’s talk, I’ve thinking more seriously about how X and Frontier could live together. I think I’ve come up with something that could work. I guess it’s time to pivot and see what happens…
P.S. No, I’m not going to tell you what X is 🙂