Christensen on Innovation

Dan Gillmor summarises Clay Christensen’s (author of “The Innovator’s Dilemma”) talk at a Harvard Business School conference:

Middle managers decide which ideas get carried forward. Senior managers don’t see the ideas first. What happens too often is that middle managers only propose things they think will be successful — and don’t propose things they believe senior management will reject. The proposals that get forwarded, he says, look like the ones that have been approved before.

“It doesn’t need to be that way,” he says.

Ideas need to go through different evaluation processes, he says. The ideas that reinforce existing things should go through one, and ideas that are disruptive should go through another.

Strategies for new opportunities: The ideal customers for a new idea are not already customers.

Johnson & Johnson’s medical device business acquired disruptive technologies. Litmus test: “Does it allow larger population of less-skilled people to do things?” All growth has come from those businesses, he says.

As it turns out, the last paragraph is what I have taken as the base for the Tech Talks in the coming week – Technology’s Next Markets.

Other notes from the conference: Kevin Marks, Denise Howell.

A few interesting points from Kevin Marks’ blog on what Christensen had to say (and which are very relevant for us in Emergic):

You need to recognise disruptive situations – there is an asymmetry of motivation, which is easier in a new business.

When you enter a market, the established competitors are motivated to leave if there is an asymmetry of motivation – if they have a place to move to that is higher margin they will. With a sustaining tech the incumbent will win about 100%. You need to harness the asymmetry.

Current customers are no good for a new opportunity. A type 1 disruption is finding the new, low cost market that the established busines doesn’t want. eg personal computer vs minis/mainframe.

Type 2 disruption is compete against non-consumption – find a new plane of competition. Cisco packet switch not good enough from telephony to start with, so market was open.

Non consumers are the ideal initial target.

Market segmentation obscures the targets for innovation – segment by goal, not by demographic.

Choosing a team – standard way is to use adjectives like visionary etc. Skills are developed by the problems they have previously wrestled with. In a successful business, the problems they have wrestled with aren’t the right kind for new growth companies. Look for experiences needed to be successful in a new business. Need to provide these experiences.

How do you compensate a disruptive team in a large organisation? Hasn’t seen correlation with stock options – offer excitement of building something big and new.

Adds Halley Suitt:

Yesterday, at our conference Clay Christensen was talking about how Sony put little cheap, crappy, transistor radios in the pockets of kids’ bluejeans when rock and roll was new and their parents didn’t want them listening to rock and roll or even wearing bluejeans. I remember listening to WABC and Cousin Brucie on a little radio like that. He was talking about competition. He was explaining how Sony sussed out the fact that they were competing against non-consumption. That is, they weren’t getting these kids to replace a table top radio like their parents owned. They were getting these kids to buy something they really wanted that they’d never bought before and therefore, they were competing against nothing. Imagine the freedom you have when you are the only guy in the game and you’ve hit on something someone really wants and will pay you whatever price to own.

Then he talked about voice recognition software and the picture of an administrative assistant on the box, looking thrilled to wear a little headset and use this impossibly clumsy software, which instead of simply typing 80 words per minute with 99% accuracy, she could now learn to talk really SLOWLY and have a 60% accuracy rate and spend lots of time making the software work instead of using something that did work for her.

He said one thing that stuck with me. Maybe you should consider making a product that does something people really need to do and helps them do it easily. Maybe you should sell products people actually need.

Continue reading Christensen on Innovation

Open Source Requirements Management Systems

A Slashdot reader has put together a wishlist of his needs:

  • Has to be web based. We are going to be spread all over the country and i see no other realistic way of doing it.
  • Has to handle multiple projects
  • I want it set up so I can take the tree of requirements, click on a button and have it take a snapshot of those requirements and mark them as the requirements for version 1. I can then still use the original requirements tree to create the requirements for version 2.0, in the future. I then want the ability to compare the two snapshots and generate a report that I can give to marketing which says: “these are the changes from version 1.0 to 2.0”
  • I want the defect tracking integrated into it. Source code management I don’t really care about, but bottom line, I want to be able to click on my snapshot of version 2.0 and run a report that itemizes everything in it, from requirements to bug fixes. I want to be able to look at a closed bug and see what release of the product it was integrated into. on this level, I really don’t give a rats @$# about what version of data.h the fix was integrated in.
  • If I have a bug reported in version 1 of a release, I want it to flag the developers of version 2 that this may be an issue for them as well. Basically have a little bit of AI as far as who needs to know about a bug, and make sure to incorporate the fix for that bug into future releases.
  • I want security set up so there is a free communication during the process of requirements management. anyone who is anyone will be permitted to add input to new feature ideas using this system. the Development Director for the particular project would be the only one permitted to make a suggestion a requirement.
  • I want an impact tree. I want to be able to run a report to show the CEO that if he wants to change the encryption from Blowfish to AES, its going to impact these requirements.

  • We have used Outreach internally and it looks good. A quote from Paul Gillingwater, Lanifex: “It was really developed as a way to allow us to keep in touch with multiple customers and partners for various projects, and includes incident management, a knowledge base, bulletin board, document repository with versioning and notification, and a handy e-mail archiving system too. It has a few plug-in options, including a GANTT tool, and an on-line update capability. It uses LAMP, but will also run under Windows if you’re able to set up MySQL, Apahce and PHP correctly.”

    Other suggestions included: Alexandria, Aegis , Wiki+Bugzilla, Tutos, Jira, Tigris, PhpProjekt, CVS.