
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:
Organizational Firefighting- Sometimes companies or projects get into trouble, and "fires" erupt one after another. When
this happens, we say we're in "firefighting" mode. But it's more than a metaphor — we
have a lot to learn from wildland firefighters.
Intentionally Unintentional Learning- Intentional learning is learning we undertake by choice, usually with specific goals. When we're open
to learning not only from those goals, but also from whatever we happen upon, what we learn can have
far greater impact.
Down in the Weeds: II- To be "down in the weeds," in one of its senses, is to be lost in discussion at a level of
detail inappropriate to the current situation. Here's Part II of our exploration of methods for dealing
with this frustrating pattern so common in group discussions.
Top Ten Ways to Make Meetings More Effective- Meetings are just about everybody's least favorite part of working in organizations. We can do much
better if only we take a few simple steps to improve them. The big one: publish the agenda in advance.
Here are nine other steps to improve meetings.
White-Collar Contractor Sabotage- Modern firms in competitive, dynamic markets draw on many types of employer/employee relationships,
including contractors. By providing privileges and perks preferentially among these different types,
they risk creating a caldron of resentments that can reduce organizational effectiveness.
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
Coming 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.
And on October 8: Responding to Workplace Bullying- Effective responses to bullying sometimes include "pushback tactics" that can deter perpetrators from further bullying. Because perpetrators use some of these same tactics, some people have difficulty employing them. But the need is real. Pushing back works. Available here and by RSS on October 8.
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
My blog, Technical Debt for Policymakers, offers
resources, insights, and conversations of interest to policymakers who are concerned with managing
technical debt within their organizations. Get the millstone of technical debt off the neck of your
organization!
