Tag Archives: Bassadur

The Hopper and the Innovation Pipeline

30 Jan

I want to talk a little bit about something we’ve done recently in the Northeast Regional Computing Program (NERCOMP). NERCOMP, like any organization, is faced with a tension between doing things now and doing things later. We’re trying to direct our energy and attention to existing, operationalized activities, while still making sure we save a little bit for new ideas that may one day become wonderful and important activities in their own right. This is trickier than it seems, because it takes a different quality of mind to keep things going than it does to recruit and envision and cultivate new things to do. But you need to do both, because you need to be successful in the present, of course, and you also want to be successful in the unpredictable future.

There are two basic knots of problems you face when you try to both have new ideas and maintain existing services. One relates to the new ideas: How do get them? Where do you put them? What do you do with them? How do you turn them into something real? The other comes from the antagonistic relationship between new ideas and existing operations. How do you keep the crazy, zany, emotional, fad-like, breathless quality of new ideas from disrupting the staid, responsible, serious work of operations, and vice versa–how do you keep the harsh noon-day realism of what exists from prematurely scorching the delicate nocturnal tendrils of the new thing being born?

The solution, in my mind, has two parts: first you need a place to put ideas, and second, you need a process that tells you what to do with them. NERCOMP, I’m proud to say, is working on both.

The Hopper

How do you get these ideas? Who knows when an idea is going to pop into someone’s head, and who knows whose head it will pop into? Apart from those rare people who continuously sprout ideas regardless of how they’re received (I’m one of them), how do you make people comfortable even saying their ideas out loud, given that new ideas tend by definition to sound somewhat crazy? How do you create a culture that says proposing ideas isn’t just OK, but expected?

Well, we’re not totally sure about the answers to any of these questions. But here’s what we did: we thought we might at least lower to the minimum the work someone had to do to get an idea from their head into ours, such that while they’re still in the thrill of the moment, and before they’ve thought better of it, they can dash it off, and we can capture it. We took a simple, one-text-box Google form, put it online, and tested it with our board members, by having them pull it up during board meetings and other NERCOMP activities. Anytime they had a thought or suggestion, they could put it right into the form. We called it the Hopper, because that name made some of us envision a kind of rotating tube full of crazy ideas, like the cylinders of ricocheting ping-pong balls used famously in lottery drawings or bingo parlors. And it worked. We gathered over a hundred ideas in a matter of weeks; too many to process, really, so we stopped encouraging it for a bit while we come up with a way to regularly review and process the contents. Now we have such a process, so we’ve made the Hopper open to all NERCOMP members (here, if you’re a member) and are poised to announce it beginning with our upcoming annual conference.

The Innovation Pipeline

Getting the ideas is the first part of the battle. But then you need to know what to do with them. Here we were influenced enormously by the work of Dr. Min Basadur, whom I’ve written about before. He breaks creative problem solving into four stages– Generating, Conceptualizing, Optimizing, and Implementing. In the first step you think of the idea; in the second you flesh it out, as it were, in theory; in the third you begin to take that theory and make a plan for its implementation in the real world; in the fourth, you implement the plan.

We took Basadur’s stages as a kind of growth chart for our ideas, if you will, and let the stages tell us what we should be doing for and with ideas as they evolved. We added transition points or firewalls between phases–places you have to check in with the board to move on to the next phase. We made these check-ins progressively more difficult. Moving from having an idea to developing it (or “conceptualizing”), we thought, really only required an interested person willing to think it through. But moving from development to optimizing (which we renamed “testing”) required a legitimate plan for the test. And moving to the final phase–implementation–required data from a successful test as well as some clear ideas about where the resources would come from to operationalize the activity. We called the whole thing the “Innovation Pipeline,” and you can see one of our early (somewhat silly) versions as we were developing it.

The Innovation Pipeline has a lot of great benefits. Most importantly it addresses aforementioned problem knot number two: it protects new ideas from operations and operations from new ideas. It trains us to modulate our expectations and behaviors and feelings towards ideas as they grow–we’re gentler on the new ideas, and we ramp up the prosecutorial rigor as they come closer to operationalization, as is only appropriate. We delay, as they say, our evaluation of ideas–we don’t burden them with premature expectations of perfection. By the same token, there are three check-in points that an idea has to get past before it can really be considered operational and thus rightly become part of our routine activities, and, effectively, force us to drop or reduce some other activity to allow for it. These three check-in points are like police road blocks. Nobody gets by who shouldn’t, thus protecting our fragile operations from the threat of disruption by frivolous novelty. A secondary benefit of the pipeline is that, surprisingly, it helps people get along better. A key flashpoint in every organization is between what the creativity researchers call the ideators (people who generate cascades of possibility and love brainstorming meetings) and the evaluators (people who say no to everything new in order to continue to say yes to what they are already doing): in our pipeline the ideators get their space to think of and develop ideas before they hand them off (at stage 3) to the testers and implementors, who are ruthless. But the ideas by then are ready for reality.

In any event, there you have NERCOMP’s approach to the age-old problem of new vs. existing activities. We’re implementing it now, and we expect some iterations and tweaks before it’s perfect. A key test will be when our rank-and-file members embrace it and put ideas in the Hopper that really challenge us to grow, be creative, and innovate. Will we be able to rise to the bold new vision they propose? Only time will tell. It’s a start, and we’ll report along the way.

As a P.S. let me give a shout out to the Learning Organization Academy–NERCOMP’s intensive new professional development program. It was LOA thinking (“how can we learn better as an organization?”) that led us to tackle the problem in the first place, and research for a LOA workshop that pointed us to a solution.

Advertisements

Being Creative Together

12 Jun

Have just read Min Basadur’s article “Leading others to thinking innovatively together: Creative leadership,” in The Leadership Quarterly 15 (2004). It’s interesting!

Basadur suggests that the big task before all of us in this global, fluid, disruptive age is to manage our organizations for adaptability rather than for efficiency (the traditional focus). Adaptability requires being creative together. We’re not good at being creative together, however; says he: “the attitudes, behaviors, and skills necessary for creative thinking are underdeveloped in many people” (106).

There is fortunately an easy-to-understand creativity life-cycle or process that’s made of four stages, each with its own kind of thinking, and people, it seems, orient to one of these stages by preference (111). The stages are Generating, Conceptualizing, Optimizing, and Implementing (112). (Which, I note, seem to generally correspond to the Learning Cycle and areas of brain processing; see my previous post on the topic.)

The problem is that, not knowing the different phases of creation, nor their preference for one or the other, people generally jumble all the phases together, achieve naught, and annoy each other.

Basadur describes the kind of meeting this leads to as “undisciplined discussions where facts, ideas, points of veiw, evaluations, action steps, and new problems are interjected randomly” (110). The person oriented to optimize, which calls for “rational, systematic, and orderly analysis” of a project-moving-towards-implementation, for instance, is not open to the incomplete and weird ideas unleashed by the person oriented towards generation (I have that orientation, for the record), who uses engagement with the world, emotions, empathy, and other unpredictable things to concoct “problems, opportunities, and projects that might be worth solving” (112, emphasis mine).  This of course, leads to the famous “how to kill ideas” situation, which Basadur describes as an insufficiency in the basic creativity-thinking skills of “deferring judgment, keeping an open mind, and thinking divergently” (106).

On a side note, Basadur aligns with Chris Argyris in seeing defensive reasoning as another block to creativity: people, says Basadur, “wait for others to find problems for them to solve,” (108); avoid “unsolvable” or cross-functional problems (108); desire to be seen as “practical and economical above all things,” and thereby tend to shut down strange new ideas (106); and “get mired in arguments about functional issues to protect their ‘turf'” (110)–all different ways of prioritizing political safety over productive thinking and creativity. Not good in an age of change.

The way to slash through all this is simply to help people with process.  A leader who knows the phases of creation can act as a creative “process coach” (111) making sure the group knows and honors the phase they’re in and uses and appreciates the particular cognitive skills the phase requires (106).  A good process-focused leader can even go so far as to predict the kinds of help individuals would need based on their orientation, and be prepared to supply that. Such a leader helps the strong optimizer, for instance, “discover new problems and facts.” In my own case, my creatively-oriented leader would help me (the generator) “convince others of the value of [my] ideas and push [me] to act on them” (116).

Importantly, Basadur notes that the highest-performing teams include a representative mixture of people orienting to the four phases of creation (115). But he also notes that people tend to gravitate towards people of like orientation, such that work teams and even professions tend to be made up of one dominant orientation (117). AND he notes that people report higher satisfaction in teams where they’re with birds of a feather (115). So there’s some natural resistance to be overcome: the leader has to consciously combine people with different orientations and help them work together; the diverse team “may experience more frustration initially” but “will achieve more breakthrough results as they learn to mesh their styles” (117).

There are some work-related processes that probably don’t fall under creation (maintenance of existing functions), but these seem less important now than in static environments of years past; Basadur’s model seems helpful for a wide breath of challenges we face at work, and should make up part of any workplace’s ethos. Thinking about the normal flow of creative–or cognitive–process  in the development of ideas and initiatives, and seeing our own orientation towards phases within that process seems particularly helpful.