
An important technique for elevating the quality of the output of brainstorming sessions is to stop doing the things that degrade quality. That's good news, because not doing something rarely costs much. In Part I of this series, we looked at changes to make before the session starts. In this Part II, we examine changes in the conduct of the session itself.
- Maintain psychological safety
- If we want people to contribute fresh, potentially radical ideas, they need to feel psychologically safe. Safety is the degree to which group members, as a whole, believe that personal risk-taking will not lead to harsh judgment of the risk-taker by the group. The brainstorm structure provides safety by prohibiting evaluation of contributions during the session.
- Evaluation If we want people to contribute
fresh, potentially radical ideas,
they need to feel safecan come in many forms: ridicule, derisive laughter, incidental comments prefatory to making contributions, and so on. Ruthlessly enforce the nonevaluation rule. - Ensure that scribing is fair
- The scribe's duty is to capture honestly the contributions of participants. Honest mistakes do happen, but a pattern of biasing the record of contributions eventually causes some to object. If biased scribing continues, some will simply stop contributing.
- Intervening when this happens is the facilitator's duty. The matter can be so delicate that recessing for a private chat with the scribe might be advisable. If interventions don't work, replace the scribe. If the facilitator fails to intervene when a scribe intervention is needed, have a private chat with the facilitator.
- Have enough scribe capacity
- When some scribes cannot keep up with the pace of contributions, they compensate by omitting some contributions, condensing them, or combining them with others. When this happens, contributors can feel devalued, and some will stop contributing.
- If the scribe is slow, and can't speed up, replace the scribe. If the contribution pace is too rapid (a wonderful problem to have), add an additional scribe.
- Name contributions descriptively
- When we name contributions to refer to them in conversation, using the contributor's name risks interfering with psychological safety when others contribute alternative ideas, or when someone credits the wrong contributor.
- To refer to a prior contribution by a name, use something descriptive of the contribution, rather than the name of the contributor.
- Allocate airtime fairly
- In some brainstorming sessions, a few individuals dominate. Reticence on the part of others can result.
- The few individuals who are dominating might be simply uninhibited, eager, well-meaning souls. If so, try a polling technique. Go around the group repeatedly, restricting each person to either making just one contribution, or passing. The more difficult situations relate to individuals whose intent is to prevent others from contributing, or who insist on evaluating the contributions of others: "I already said that," or "We tried that," or "That will never work." Address these difficult situations proactively by establishing behavioral norms at the outset, and by intervening, perhaps privately, in the case of repeated norm violations.
None of these practices guarantees better brainstorming results. People can be very creative about finding ways to stifle creativity. First issue in this series
Top
Next Issue
Do you spend your days scurrying from meeting to meeting? Do you ever wonder if all these meetings are really necessary? (They aren't) Or whether there isn't some better way to get this work done? (There is) Read 101 Tips for Effective Meetings to learn how to make meetings much more productive and less stressful — and a lot more rare. Order Now!
Your comments are welcome
Would you like to see your comments posted here? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend 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.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
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.
Related articles
More articles on Personal, Team, and Organizational Effectiveness:
Make Space for Serendipity
- Serendipity in project management is rare, in part, because we're under too much pressure to see it.
If we can reduce the pressure, wonderful things happen.
When We Need a Little Help
- Sometimes we get in over our heads — too much work, work we don't understand, or even complex
politics. We can ask for help, but we often forget that we can. Even when we remember, we sometimes
hold back. Why is asking for help, or remembering that we can ask, so difficult? How can we make it easier?
Selling Uphill: Before and After
- Whether you're a CEO appealing to your Board of Directors, your stockholders or regulators, or a project
champion appealing to a senior manager, you have to "sell uphill" from time to time. Persuading
decision makers who have some kind of power over us is a challenging task. How can we prepare the way
for success now and in the future?
The Risks of Too Many Projects: II
- Although taking on too many projects risks defocusing the organization, the problems just begin there.
Here are three more ways over-commitment causes organizations to waste resources or lose opportunities.
Red Flags: II
- When we find clear evidence of serious problems in a project or other collaboration, we sometimes realize
that we had overlooked several "red flags" that had foretold trouble. In this Part II of our
review of red flags, we consider communication patterns that are useful indicators of future problems.
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
Coming September 24: Time Is Not a Resource
- In the project management community, it's often said that time is the most precious resource. Although time is indeed precious, to regard it as a resource — like finance, equipment, or people — can be a dangerous mistake. Time is not a resource. Available here and by RSS on September 24.
And on October 1: On the Risks of Obscuring Ignorance
- A common dilemma in knowledge-based organizations: ask for an explanation, or "fake it" until you can somehow figure it out. The choice between admitting your own ignorance or obscuring it can be a difficult one. It has consequences for both the choice-maker and the organization. Available here and by RSS on October 1.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
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-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
