Christensen's Innovator's Solution – 50 Book Challenge

I committed to the 50 book challenge last month. I'm moving along with the reading, now I'm trying to get current with writing about it. Here's the first write up. I'm not quite sure how I'm going to organize this, beyond the posts themselves. We'll see what develops.

 

The Innovator's Solution: Creating and Sustaining Successful Growth
Christensen, Clayton M.

Christensen's The Innovator's Dilemma was easily one of the best business books I've read in the past 10 years. The Innovator's Solution is in the same category. I suspect we'll look back in a few years and place this work in the same seminal category that Michael Porter's books on competitive strategy acquired in the 80s.

Christensen's work sytematically addresses the problems I wrestled with in working with Porter's conception of strategy. Porter's work is rooted in classical industrial economic analysis, which by and large focuses on questions of equilibrium. I could never see how to connect that work to the dynamic, technology driven environments I worked in. Christensen addresses that in very powerful ways.

One of the aphorisms I took to heart from The Innovator's Dilemma was “markets that don't exist can't be analyzed.” In this book, Christensen begins to lay out how you can take the notions of disruptive innovation and use them to design a reasonable course of action in the absence of the kind of analytical data strategy consultants desire.

He returns to his original distinction between sustaining and disruptive innovation. As he takes pains to repeat, these are not synonyms for “incremental” and “breakthrough.” Christensen is interested in the market impacts of an innovation, not in its technological pedigree. Regardless of its technological difficulty, an innovation is sustaining if it is designed against the performance criteria of existing customers and markets; particularly the criteria of the most advanced and demanding customers.

Disruptive innovations attack either the lower ends of existing markets where there are customers willing to settle for less performance at less cost, or new markets where a new packaging and design of available technologies creates an alternative to non-consumption. The example I found easiest to understand here was Sony's invention of the portable transistor radio. Compared to vacuum tube radios the first transistor radios were crappy, but good enough for teenagers and others on the go whose alternative was no music at all.

A well concieved disruptive innovation attacks a market that existing competitors would happily abandon (customers who complain that your products are too complex and expensive for their basic needs) or do not see. This keeps you off the radar while you build a market and improve the performance of your product.

Christensen's approach also suggests some counterintuitive approaches to launching innovations intended to be disruptive. In particular, he argues convincingly against trying to get big fast in favor of seeking profitability early on. I need to think some more about that and see how you might account for something like Amazon in his framework. Which would start with deciding whether you would consider Amazon to be a sustaining or a disruptive innovation. I think I could argue either side. Regardless, I suspect that this is a book that like Porters', I will read several more times before I figure it all out.
 

The spreading virus of IP law

the spreading virus of IP law. So after being battered down again and again, the database bill is back. Congress is again being pressed by IP extremist lobbyists to “solve” the “problem” of “inadequate legal protection” for databases by adding a raft of IP lawyers into the mix. This is an awful law, and were the attention of good people everywhere not focused upon the many awful things happening in DC, it would be dead on arrival. But unfortunately, it lives. PublicKnowledge is doing its part to stop it. Please do something to help stop it again. [Lessig Blog]

Do you ever wonder whether any of our legislators were awake in their Constitutional Law classes?

Organizational silence and its costs

Speak freely. Jevon MacDonald on organizational silence and its costs.

[Seb’s Open Research]

Key graf:

Organizational communications are at the mercy of corporate culture. The more top-down our methods (newsletters, presidents reports, corporate newspapers) of communicating and directing, the more we formalize (by implication) our less structured interpersonal communications. Even the validity of our consensus building exercises comes in to question when we realize that our corporate culture may be fostering silence within the hierarchy.

Very thought provoking piece. One of the frustrating aspects of organizational silence is how easy it is to provoke even when senior executives are desperately in need of more open communication and would welcome it if they got it. What they tend not to see is how they contribute to silence instead of voice. It’s hard in the midst of all the more obvious pressures they face.

Who's working on Personal Information Management?.

Who’s working on Personal Information Management?. These are two very valuable overview documents. Many thanks to Piers Young for pointing to them, and to Richard Boardman (Imperial College London) for writing them!

[Seb’s Open Research]

And thank you Seb for passing it along.

Rational ignorance

Rational ignorance.

Lago

Rational Ignorance

Academic life is ruining the internet for me. An example: Today I read Joi Ito s wandering entry on money, economics, and physics, and the first thing I thought of doing was to post a bibliography of all of the reading that should have been done before that post was made. And then I realized that posting such a bibliography is the equivalent of shouting at the television. It doesn t matter what I say about it. The TV (and the internet) can t really hear me.

Lago reacts to an interesting point that I in fact pondered yesterday before posting my thoughts from my lunch with Seth. Is it better for me to post my superficial musings with Seth in the one hour that I had before I needed to move on to the next thing, or do I scribble them in my notebook and write a more rigorous treatment with references. I decided, as Cory often says, that my blog is my notebook and that even though many of my thoughts were half-baked, it was better to write early/write often than to back burner the thoughts and probably never get around to posting them.

[…snip…]

I don’t want to ignite a academic vs non-academic flame-war here. I’m just trying to point out, as Lago does, that we are all making decisions about how much to study in order for us to make the right decisions. I don’t have the time or the ability to do “all of the reading that should have been done before that post was made.” Having said that, I would encourage people to post “a bibliography of all of the reading” since I am interested and so are many other people.

By Joichi Ito joi_nospam_@nospam_ito.com. [Joi Ito’s Web]

Interesting ruminations from Joi Ito on how to strike a balance between getting something out the door and thinking some more about it.

I feel that I tend to err in the other direction of sitting on things too long instead of putting something out there, although the experience of weblogging over the past two years has helped immensely in moving toward Joi’s position. It’s something I find myself thinking about explicitly far more than I used to.