When controversy is in the air, or the group is large, the flow of discussion in meetings can become confused and tangled. Even when facilitators manage queues of contributors, separations between related contributions grow, threads proliferate, and people forget what they wanted to say as they are overtaken by events.
When the threads of discussion become tangled, the group's decision quality degrades. Reaching decisions becomes a long, painful process. How can we keep threads from tangling, or untangle them when they tangle?
- Use a parking lot
- Sometimes a collection of contributions isn't really essential to the current discussion. Or perhaps it's important, but missing information or absent staff prevent a definitive conclusion.
- Threads of this kind can be profitably deferred using a technique widely known as the parking lot. Deferring the topic by adding it to a parking lot, or issues list, clears the table, making way for the larger discussion to move forward more effectively.
- Identify questions masquerading as assertions
- One common source of controversy is the question masquerading as an assertion. Some contributions are assertions or conjectures that, although possibly correct, are nevertheless unproven. When controversy is in the air, these contributions tend to generate much energy but little light.
- By identifying statements that are actually open questions, the group can focus its discussion on resolving the questions, possibly at a later date, rather than endlessly circling around a loop of assertions and counter-assertions.
- Name and rank the threads
- Once a collection of contributions emerges as a thread, allowing it to continue as a part of the ongoing discussion creates a risk that it will tangle with other threads.
- By giving each thread a name, and setting priorities for each, the group or its facilitator can give focus to a single thread, temporarily setting others aside. This leads to a more orderly discussion.
- Maintain multiple queues
- Once you've named threads, and ranked them, arriving contributions can be queued independently for any threads that aren't currently under discussion. Maintain a separate queue for each thread.
- This scheme is more effective when participants make notes for themselves about the contributions they intend to make to threads that have been temporarily set aside.
- If a single thread, or a
collection of threads, becomes
complex enough, it merits
a discussion of its own - Spin off independent discussions
- If a single thread, or a collection of threads, becomes complex enough, it merits a discussion of its own. To keep it as part of the discussion that spawned it entails risk of confusion.
- Make it an agenda item, at this meeting or at a future meeting. Accomplishing this might require deleting or postponing other items from the existing agenda.
Even these measures have limits. Large groups engaged in especially controversial conversations might have to break into smaller caucuses, in parallel or in series, to address the most contentious issues. Groups that can't agree on how to manage their discussions probably can't agree on much else. First 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? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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:
- Achieving Goals: Inspiring Passion and Action
- Achieving your goals requires both passion and action. Knowing when to emphasize passion and when to
emphasize action are the keys to managing yourself, or others, toward achievement.
- Clueless on the Concept
- When a team member seems not to understand something basic and important, setting him or her straight
risks embarrassment and humiliation. It's even worse when the person attempting the "straightening"
is wrong, too. How can we deal with people we believe are clueless on the concept?
- How We Waste Time: II
- We're all pretty good at wasting time. We're also fairly certain we know when we're doing it. But we're
much better at it than we know. Here's Part II of a little catalog of time wasters, emphasizing those
that are outside — or mostly outside — our awareness.
- Red Flags: III
- Early signs of troubles in collaborations include toxic conflict, elevated turnover, and anti-patterns
in communication. But among the very earliest red flags are abuses of power. They're more significant
than other red flags because abuses of power can convert any collaboration into a morass of destructive
politics.
- Anticipating Absence: Passings
- In times more normal than ours, co-workers who pass on tend to do so one at a time. Disease or accidents
rarely strike many co-workers in the same week, month, or year. There are exceptions — 9/11 was
one such. This pandemic is another.
See also Personal, Team, and Organizational Effectiveness, Effective Meetings and Conflict Management for more related articles.
Forthcoming issues of Point Lookout
- Coming May 8: Antipatterns for Time-Constrained Communication: 3
- Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 3 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing past experiences of participants. Available here and by RSS on May 8.
- And on May 15: Should I Write or Should I Call?
- After we recognize the need to contact a colleague or colleagues to work out a way to move forward, we next must decide how to make contact. Phone? Videoconference? Text message? There are some simple criteria that can help with such decisions. Available here and by RSS on May 15.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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
rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed