« 8: Most new ideas aren't | Main | metacool Thought of the Day »


I think the first good idea you have to kill is your title for this principle. I like the dynamics you've described, but I don't think the title does a good job of communicating them. Plus I think it will be used as a cover for assholery - wherein I kill someone else's idea because "Diego says we need to kill good ideas". Which is not at what the principle is about, in my reading.

I think this is way too simple of a statement.
I hope it doesn’t become someone’s quick reasoning for dismissing an idea or being a jerk.
Other thoughts for idea titles:
Knowing which ideas to kill and which ideas to morph.
Don’t fall in love with your idea.
Understand how your idea works in the company

Killing good ideas can be a good idea?

This is something I have found useful working within a project, but it was also something I had to learn in the real-world. At school I could simply choose to put less weighting on constraints such as cost, manufacturability etc, so that I could continue to develop my 'good idea'.

Learning when to take a step backwards and let-go of an idea (knowing more than I did when I started the project) can result in a faster path to a more appropriate solution.

This is good, especially in light of the fact that it is very difficult for most companies to kill bad projects, let alone good projects.

Diego - have you studies Toyota and the Toyota Production System? One thing not highlighted enough in innovation circles is how Toyota empowers tens of thousands of people to solve problems innovatively and simply: the difference between thousands of small rocks versus a few big rocks is a philosophical one, but one that defines a culture of innovation across groups of people, or a few select heroes.

Pete Abilla

The comments to this entry are closed.