![]() |
Vinod's Blog Random musings from a libertarian, tech geek... |
|
I read Innovator's Solution over the Thanksgiving holidays and was impressed with the book. It's a worthy successor to Innovator's Dilemma and picks up cleanly where the first left off. Clayton Christensen (along with his new co-author Michael Raynor) has built himself quite a franchise and has pulled off the rare fete of creating a follow up work as good as the much heralded original. The authors quickly state the core problem they're trying to address [p 1..7]:
Pretty stark odds, he? The book presents an excellent discussion of why this is the case and what mistakes managers systemically make. One of my biggest criticisms of the model in Innovator's Dilemma was that it didn't present a good model for:
This distinction is crucial for managers planning actions in the face of new technology. The authors address this issue rather satisfactorily using the framework that product boundaries are the result of "jobs to be done" rather than "technologies available" [p 85]:
So a new technology is additive if it's addressing a new job and disruptive if it eventually addresses the same old job as a previous technology. Now, I know that when presented abstractly like this, a lot of business boils down to common sense and relatively simple observation. And, folks who don't LIVE the tech biz world often read some of this stuff and say "that sounds pretty obvious". But the real contribution of Christensen / Raynor is the precise codification of something we may already intuitively know in limited circumstances. We may recognize some of the phenomena under certain circumstances but until it's codified, there are many, often significant cases where we tend to miss it. Industry adventures with Interactive TV, cell phone + PDA's, DVD + CD players, network computers, etc. are all obvious failures in hindsight but didn't seem so at the time. Christensen / Raynor provide an excellent treatment of how architectures define the selection integrated and modular systems. Most of my blog trends towards political rather than econ so I can't resist bringing in the politico-economic message. Many activists (particularly of the Left Wing ilk) believe that the existence of monolithic architectures in the market is the result of some dark conspiracy by the entrenched power elite who are able to collectively block alternate architectures from entering the market (Microsoft vs. Linux, Oil companies vs. "the hydrogen economy", Meat vs. Soy, etc.). Christensen & Raynor provide an elegant theoretical model for when vertically integrated technical markets persist, how they become modularized and what mechanisms exist that cause the entire system to fall by the wayside (eventually). The Politico in me loves the fact that they've articulated a rather comprehensive model where the only abject display of Power is that which is exercised by the consumer. Producers beware! They authors somewhat expressly stay away from stating a direct opinion about the Microsoft anti-trust case (walking into that minefield would almost certainly detract from the primary mission of the book). BUT an astute reader looking between the lies can get a good idea of where their sympathies lie [p 135]:
The core strategy they recommend for the Microsoft's in various industries? The need to be willing to experiment with corporate intrapreneurship BUT, as the "board" for a new venture, do NOT expect massive growth immediately but instead focus marginal profitability. Be patient about growth but not about profits. Growth patience is meant to encourage the new venture to seek emergent opportunities rather than attempting to "bat one out of the park" on every swing. Being receptive to emergent strategy helps the venture managers stay open to serendipitous opportunities. Being focused on immediate profitability helps ensure that they always mine them. A great footnote captures a phenomena that Silicon Valley rank-and-file often see in our VC backers [p 234]:
(By the way, in stark contrast to most books where the footnotes are simply long lists of bibliographic citations, the notes in Innovator's Solution are illuminating and truly add substantial texture. I HIGHLY recommend reading ALL of the chapter footnotes in detail). Overall, Innovator's Solution is one of the best business books I've read in a long time although perhaps a notch shy of the ground-breaking nature of it's predecessor. Nevertheless, I suspect it will become a "new classic" oft-cited by technology managers and observors alike. ![]() |
|
| ||