Bringing Tech to Market: The Rules of Innovation

Everyone knows that best-quality plus first-to-market doesn't always equal success. A Harvard prof who specializes in this stuff has a great article in Technology Review that digs a lot deeper, called The Rules of Innovation. It's a look at why some technologies are marketplace success stories and some are forgotten failures -- and more, an attempt at rules which predict which will be which. There are lessons here for the entrenched companies (e.g. Sony) as well as for the disruptive upstarts (e.g. Sony 50 years ago). You have to understand the battlefield to win the war.

Comments

Point 4 is the only significant factor

[gelfling]

If the transition costs you impose on your customers is too high they'll run for the door screaming. It doesn't matter how wonderful your technology is. That's why DIVX and HDTV are dead or dyeing for example. You can't make it so hard to use or purchase or install that only primary adopters use it.

cough cough hack linux cough bsd

That's the lesson of desktop linux - it doesn't matter HOW BAD MS is - what matters is HOW HARD the transition to something else is.

I Don't Believe Him

[CaptainCarrot]

It's not uncommon that I encounter articles such as this one where I know very little about the subject being discussed, but I do know a bit about some of his examples, and they are sometimes faulty.

Take his criteria for a successful disruptive technology. I can't help but observe that the light bulb, a successful innovation if ever there was one, satisfies neither. The answer to 1 is negative because neither the poor nor the wealthy were capable of lighting their homes with electricity at the time. Likewise the answer to 2 because there was no existing market. Yet this technology was undeniably disruptive; just ask the manufacturers of candles, oil lamps and gaslights.

Later on in discussing (as far as I could tell) allocation of resources, he says, "Processes, however--the central element in our second question--are typically inflexible. Their purpose is not to adapt quickly but to get the same job done reliably, again and again." He must be completely unfamiliar with the Software CMM (and now the CMMI for other disciplines) where to attain the highest rating and organization's processes must be flexible. Continuous improvement of processes is one of the more important lessons from the quality movement Prof. Christensen discusses in the opening of his article, so I'm a little surprised he chooses to ignore it here.

This leads me to suspect that some of his other examples are flawed too, but I don't know enough about all of them to detect it. I don't trust his conclusions, in any event.