New Ideas: Generation
by Rick Brenner
When groups work together to solve problems, they employ three processes repeatedly: they generate ideas, they judge those ideas, and they experiment with those ideas. We first examine idea generation.
XP-80 prototype Lulu-Belle on the ground, in a photo probably taken in 1944. Although this aircraft wasn't the first US jet-powered aircraft, its operational version, the P-80 later designated the F-80, was the first operational jet aircraft to have its engine integrated into the fuselage. It arrived too late for combat in World War II but it did see service in Korea.
The XP-80 was developed as the first project of the Lockheed Skunk Works, which was a facility established by Lockheed to enable development of advanced aircraft. The concept of a skunk works, now widely used in business, is that by giving innovators autonomy, and protection from bureaucracy, we can accelerate development. A skunk works is the organizational analog of what idea generators need when groups solve problems. Photo courtesy United States Air Force.
To solve problems, groups need good ideas. Since complex problems usually require many good ideas, we generate them any way we can — brainstorming, conversations over lunch, or even dreaming. The ideas we generate include the good, the bad and the ugly, and it isn't always obvious which is which. We have to comb through them all, evaluating, assessing, doing thought experiments, and making judgments. When we think we've found something worthwhile, we might do some actual experiments to help with the judging.
Generate, judge, experiment. Generate, judge, experiment. It isn't a simple cycle, of course, because sometimes we generate new ideas in the course of judging, or while running experiments. Nevertheless, it's useful to consider three roles for group members: generators, judges, and experimenters. Some people hop easily from role to role, and some adopt two roles — or all three — simultaneously.
Although ideas have a life cycle, we don't always respect that life cycle, and that's where trouble can begin. Over the next three issues, I offer some insights that help us to accommodate our generating, judging, and experimenting efforts to the life cycle of ideas. Let's begin with generating.
- Newborn ideas are fragile
- Newborn ideas — ideas just hatched and new to the group — are easily crushed. They usually have weaknesses that haven't yet been addressed. They're incomplete and vulnerable.
- Their vulnerability arises from at least three sources. First, if the problem space is complex, the generator of the idea might have grasped only a part of the problem. Second, generators tend to focus on singular aspects of the problem, even if they have grasped the entire problem. Third, to aid generation, generators often intentionally produce wacky or mostly-wacky ideas, because they can trigger creative thinking.
- To prevent premature rejection of newborn ideas, suspend judging until generation has completed an iteration. This suspension is an important part of formal brainstorming.
- Addressing weaknesses requires resources
- Newborn ideas are Newborn ideas are incomplete,
in part, because of the
their constituenciesincomplete, in part, because of the narrowness of their constituencies. Because it's new, a newborn idea hasn't yet acquired advocates beyond the small circle of its generators. This is rarely enough to protect a newborn idea from rejection, as its list of weaknesses accumulates.
- When we apply our judging and evaluation processes to newborn ideas, they sometimes die because their constituencies are so narrow that they suffer from insufficient exposure to cognitive diversity. For example, their generators might not have considered a weakness identified by a judge, or even if they have, they might not have developed a resolution.
- To prevent premature rejection of newborn ideas during judging, consider designating teams of advocates to address the weaknesses judges identify. The advocates might need more members than the judging team, because addressing weaknesses can be more difficult than identifying them.
Next time, we'll examine the judging process. Meanwhile, I hope you can suspend judgment on these insights about newborn ideas. Next in this series Top Next Issue
Are you fed up with tense, explosive meetings? Are you or a colleague the target of a bully? Destructive conflict can ruin organizations. But if we believe that all conflict is destructive, and that we can somehow eliminate conflict, or that conflict is an enemy of productivity, then we're in conflict with Conflict itself. Read 101 Tips for Managing Conflict to learn how to make peace with conflict and make it an organizational asset. Order Now!
Your comments are welcome
Would you like to see your comments posted here? Send me your comments by email
, or by Web form
About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful,
and that you'll consider recommending it to a friend
Point Lookout is a free weekly email newsletter. Browse the archive
of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout,
as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in,
anonymously if you like, and I'll give you my two cents.
More articles on Problem Solving and Creativity
- Dealing with Deadlock
- At times it seems that nothing works. Whenever we try to get moving, we encounter obstacles. If we try to go around them, we find more obstacles. How do we get stuck? And how can we get unstuck?
- Assumptions and the Johari Window: Part II
- The roots of both creative and destructive conflict can often be traced to the differing assumptions of the parties to the conflict. Here's Part II of an essay on surfacing these differences using a tool called the Johari window.
- The Perils of Piecemeal Analysis: Content
- A team member proposes a solution to the latest show-stopping near-disaster. After extended discussion, the team decides whether or not to pursue the idea. It's a costly approach, because too often it leads us to reject unnecessarily some perfectly sound proposals, and to accept others we shouldn't have.
- Teamwork Myths: Conflict
- For many teams, conflict is uncomfortable or threatening. It's so unpleasant so often that many believe that all conflict is bad — that it must be avoided, stifled, or at least managed. This is a myth. Conflict, in its constructive forms, is essential to high performance.
- Hill Climbing and Its Limitations
- Finding a better solution by making small adjustments to your current solution is usually a good idea. The key word is "usually."
See also Problem Solving and Creativity and Conflict Management for more related articles.
I offer email and telephone coaching at both corporate and individual rates.
Contact me for details at rbrenner@ChacoCanyon.com
or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout
are available in six ebooks:
Reprinting this article
Are you a writer, editor or publisher on deadline?
Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough, but to project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:
- The Race to the South Pole: The Power of Agile Development
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program: