Seriously Disruptive Innovation
Seriously Disruptive Innovation
Blogger note: I’m going to take a wild guess that if you’re reading my blog you probably aren’t an avid academic journal reader. In the words of my father, “[Academic journals] may be interesting, but they never have any real-world practicality.” To which I say, “Sometimes.”
If you were to read only one journal related to innovation I’d suggest reading the Journal of Product Innovation Management that comes out of the PDMA. It’s an incredibly good journal with an eye towards the practitioner rather than just the academic.
I asked @ProfessorGary what kinds of blog posts he was interested in and one of the topics he raised is “effectuation innovation.” For some reason over the last year that term has slipped my mind, and I don’t know why. When I was working on my MBA it was one of my favorite topics inside of my program because at first glance it goes against everything that MBA programs like to preach: Research, research, research then use the market research that is statistically significant to determine your best next steps. Don’t ever shoot from the hip, and do things based purely on reason and fact.
News to MBA students: Sometimes there is no way to do market research and you just have to rely on real-time market data. This is called “effectuation innovation”. The term was coined by Sarasvathy in a 2001 paper. I’m not going to rehash the paper, but rather I’m going to give you the basics and apply it to how really high quality, disruptive startups work.
The core of the idea is this: an entrepreneur or innovator doesn’t have information because the market doesn’t exist yet. Every bit of advanced market research you’d do is going to be bunk because your potential customers have no clue why they’d buy what you’re talking about. The answer is this: go create whatever you’re going to create and then build a framework that allows you to change whatever you’ve created in response to the free flowing data you receive via real-time customer reactions.
OK, let’s talk about this in terms of a real-life example. I’m a food nut, so let’s talk about Grant Achatz’s new restaurant Next (which I have yet to get to, but am dying to try). The restaurant turns the industry on its head by doing two major things differently: 1) It is not an Italian, French, Thai or any other sort of restaurant, but rather it is a specific place and time for only 3 months at a time. So, for their opening they were Paris, 1906- so all the food was set to be from the area and what you’d get at that time. 2) You could not make traditional reservations, but rather had to buy tickets. Ticket prices would move based on the popularity of a time- so Saturday at 7pm is more expensive than Wednesday at 9pm.
This has raised a number of innovation challenges for the team. First, every 3 months their supply chain is totally disrupted. They’ve had to work with suppliers to find the ingredients to meet their needs. They’ve done this by using a wide network of suppliers from around the world.
Second, they had to develop a ticketing system that worked for a restaurant rather than for an event. They quickly realized from customer experiences that they had to create a system that allows for ticket exchanges since sometimes plans come up that change when someone can have dinner.
Achatz and his team couldn’t figure out what demand would be for this restaurant in advance, a restaurant like this has just never existed. They’ve had to play it by ear and work out the kinks as it goes. I’m sure they’ll run into new issues as time goes on, but they seem to be doing well at reacting quickly.
The moral of this story is- if you’re going to do something new, just do it and react to the market as needed to maintain a positive orientation towards the market your serving.
PS- Here’s one of my favorite writers (Phil Vettel) take on Next.
