After all these years that I've studied and taught creativity and innovation, I am starting to believe that one element of the process is tougher for many people to accept than the rest -- that it is a messy and uncertain process and efforts to make the early messy stages more rational, safer, and generally neat and clean comforting get in the way of the process.
I confess that I suffer from wanting to get rid of this messiness now and then too, and in fact, during the early days of the Stanford d.school, I went to our founder and inspiration David Kelley and asked him to make things less confusing and upsetting, and in the nicest possible way, David said he couldn't, that we were involved in messy process and if I couldn't deal with it, perhaps I should do something else. I see the same instinct in how some university administrators and faculty react to the d.school, in that the love the innovation and creativity, but the physical messiness and lack of orderliness disturbs them. Now, we have developed techniques to help people navigate the messiness more effectively (notably the Bootcamp Bootleg) but the process is still messy and uncertain.
I was thinking of this because I was reading an article by Bill Coyne, who led R&D at 3M for over a decade. I met Bill about ten years ago, and he is very wise And he understands both the messiness and misguided impulse to clean it up. I loved this quote:
Finally, don't try to control or make safe the fumbling, panicky, glorious adventure of discovery. Occasionally, one sees articles that describe how to rationalize this process, how to take the fuzzy front end and give it a nice haircut. This is self-defeating. We should allow the fuzzy front end to be as unkempt and as fuzzy as we can. Long-- term growth depends on innovation, and innovation isn't neat. We stumble on many of our best discoveries. If you want to follow the rapidly moving leading edge, you must learn to live on your feet. And you must be willing to make necessary, healthy stumbles.
Given all this, innovators still are often surrounded by people who want to give their process "a nice haircut." How can this be stopped? And perhaps I am being to closed-minded. Do any of those haircuts ever work?
Fuzzy isn't easy for anyone. Len Sweet, my mentor in my Doctoral work used one of the magic eye images to give us a reminder to go fuzzy, not looking for one solution. But perhaps more importantly to take something as a whole and not dissect it. Fuzzy means learning to "stand under" something rather than understand.
One thing I have been wondering about that you bring up, Bob...Are those who can really come to terms with the fuzziness the product of intense, under the fire, frightening as hell, kinds of experiences...who have to make something happen.
Does someone who can stomach the possibility of failure need to have looked in the face of fear and failure before? Kind of do you need to know hunger to know when you are hungry.
Posted by: Kdlbullock | June 27, 2010 at 10:36 PM
I worked in a product development dept.at infotech company many eons ago, and I recall us dreaming up the dual system of creating/innovating/experimenting in what we would call "the sandbox". Products for which we had actual revenue coming in could not be in the sandbox, they needed to go through a lean production facility in a tightly controlled timeline. The problem I ran into is telling marketing/sales that sandbox projects cannot have launch dates until we were ready to take it out of the sandbox and it could go through routine production without grit breaking down the machinery, so to speak.
I guess it is the eternal tension between "create" and "productize".
Posted by: Carol Murchie | June 07, 2010 at 10:43 AM
If these haircuts do work, I suspect that it is due to blind luck more than anything else.
As my personal experience mounts, it becomes clear that innovation is something that cannot be fully described, defined or forced. Innovation does not follow a timeline. It is something you'll know when you see it.
The true nature of innovation often upsets management, the bean counters, etc. because it cannot be controlled well.
Innovation needs to be fully embraced, in all its messiness, if real progress is to be made.
Posted by: Nathan | June 07, 2010 at 05:11 AM
Some companies use the fuzzy front end very well.No haircuts are allowed till feasibility studies are completed. They actually delay the haircuts till the contract is awarded to the vendor. This is when the fuzzy front end streamlines itself into a finely pointed tail. Engineers of well designed projects will even allow for some deviation from original specs if it is in the interest of the project.
Posted by: Daniel Christadoss | June 05, 2010 at 03:42 PM
As a software engineer I experience the the "nice haircut" phenomenon with the scrum project management process. Scrum (and every other software engineering project process I've worked on) help you get from point A to a well known and well defined point B. They all assume you know what you're going to do and just need to work out how you're going to do it.
This style matches the second half of most software projects, but not the first. The first part of a new project is all about innovation and pushing the team. Project processes stifle that creativity. The project becomes much more predictable, but also less innovative.
Giving those early fuzzy days a haircut is a good way to get from point A to point B, but it almost guarantees you'll never see points C, #, or 27.
Posted by: Zack Grossbart | June 05, 2010 at 01:04 PM