Showing posts with label clayton christensen. Show all posts
Showing posts with label clayton christensen. Show all posts

the innovator's dilemma

Before starting, the team members were invited to read a number of books and articles:

For Clayton Christensen, The Innovator’s Dilemma is that, while listening to existing customers can inhibit innovation (because they don’t necessarily know what they want or what’s good for them), listening to existing customers can be the key to survival (because they sometimes know exactly what they want and what’s good for them). The distinction has to do with sustaining and disruptive innovation and technologies. Customers are obviously better at imagining and wanting the former than the latter.

Additionally, organisations dominant in their sector, according to Christensen, tend to focus on maintaining the product and service quality that won them their customers in the first place. This leaves new entrants free to focus on developing new products, services or applications.

Because disruptive technologies are often serving entirely new markets, and because markets that do not exist cannot be analysed, established companies will tend to shy away from investing in them. Among the answers are setting up ‘innovation islands’ in large businesses, spinning off start-up groups, taking equity positions in (i.e. buying bits of) new, independent companies, and so on.

From this point of view, it looks like The Economist Group was doing the right thing when the GMC decided to stand back and give Project Red Stripe a free hand to implement whatever idea it chose without first seeking approval from Group management. But, in practice, as we’ve seen, this was an unrealistic decision. The management team needed to know if the Economist Group was about to be committed to an expensive, high-profile, not-for-profit venture.

In his book, Christensen describes at some length the innovation process in the computer hard drive manufacturing sector. He explains how it simply wasn’t appropriate in 1979 for an established computer hard drive manufacturer to get out of the 8-inch drive business (where its customers were) and into the 5¼-inch drive business (which didn’t yet exist). But the predictable result was that the established manufacturer was supplanted by a newcomer and eventually went bust. In the same way, it wouldn’t have been appropriate for The Economist to focus on a philanthropy exchange website when its magazine publishing business was doing better then ever. One answer would have been to spin the idea off and invest in it if they liked the idea enough.

(Incidentally, I notice that the first of the SIPs (Statistically Improbable Phrases) that amazon.com lists for Christensen’s book is ‘value network framework’. Not only statistically, but also linguistically, improbable, I think
.)

Dilemmas:

Most organisations don’t want to be disrupted. Many of the most significant innovations and innovation technologies have been definitively disruptive.

Listening to existing customers can inhibit innovation and also be the key to survival.


incubating innovation


In setting up Project Red Stripe, The Economist unquestionably did the right thing, according to specialists who know a lot more about innovation than I do. Jeneanne Rae and her colleagues analysed sixty recent innovations in the service industry, including in-depth interviews with key team members (How do they do that? I managed to watch one. A bit.) She wrote about her conclusions in Business Week. Her fourth (and ‘specially important’) principle is:

Techniques and structures that counterbalance the forces of risk aversion.

She explains that big enterprises are large because they’re successful and success is a barrier to innovation. Why try something new and risky when what you’re doing now works? If it ain’t broke… (which is the point I was making in Motivations about the group’s eventual decision not to go ahead with the HiSpace idea).

One of the techniques and structures that she proposes to deal with this situation is as follows:
Form a special petri-dish environment where new concepts can grow. Pitney
Bowes has a concept studio designed to explore opportunities far afield from its
existing lines of business. IBM has a similar unit, called ‘EBO’ for Emerging
Business Opportunities. This approach minimises distraction to the ongoing
business and permits concentration of special innovation skills. Successful
projects are then sold back to the business units.
A petri-dish environment is what The Economist got itself with Project Red Stripe. Furthermore, the ubiquitous Dave Pollard
quotes disruptive innovation expert Clayton Christensen describing IBM’s survival in the face of waves of disruption from advances in computer technology as being down to its use of innovation incubator units.

There are two reasons for doing this, according to Christensen:
1. Nurturing innovation requires different skills, different resources, a different benchmark of success, a different management style, less aversion to risk, and a different focus from the mainstream business.

2. Innovation can be a distraction to the mainstream business, threatening the processes and attention to traditional customers that have made the mainstream business successful.
Commenting on Jeneanne Rae’s article, Tom Foale rightly observes:
Demands from existing customers fuels sustaining, not disruptive,
innovation. Disruptive innovation can't be analysed for growth potential because
it creates new markets, so it usually gets filtered out either explicitly (it
doesn't meet growth needs) or through internal pressure for staff to perform.
Most businesses whose development teams have created disruptive innovations let
them go elsewhere -- look at Xerox for an extreme example.
There’s more on this in The Innovator's Dilemma.

So The Economist did the right thing. Whether they did the thing right is what I’m discussing everywhere else in this book.

Dilemmas:

If it ain’t broke… don’t fix it ~ If it ain’t broke, these days, it probably will be soon enough.


-----------------------------------------------------------------------------

Credits:
Petri dish: Justin Baeder

-----------------------------------------------------------------------------