Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 9, Issue 39;   September 30, 2009: Tangled Thread Troubles

Tangled Thread Troubles

by

Even when we use a facilitator to manage a discussion, managing a queue for contributors can sometimes lead to problems. Here's a little catalog of those difficulties.

In group discussions, we sometimes use facilitators to manage the flow of contributions. One technique employs a queue. During the discussion, usually while one participant is speaking, another might catch the attention of the facilitator to request a spot in the queue. In person, this can be done with a raised hand or a facial expression. In teleconferences, it might occur through a "hand-raise" channel or through texting.

A single-strand knot

A single-strand knot. This particular knot cannot be un-knotted without cutting the string and rejoining it. In this respect, it is similar to the kind of tangles that occur in multi-threaded discussions. But it differs from them in at least two ways. First, multi-threaded discussions consist of more than one strand. Second, since some contributions to multi-threaded discussions belong to more than one thread, the threads of discussions are sometimes joined to each other at one or more points. Untangling a discussion is thus a much more complex problem than unknotting strings. Image by Robert G. Scharein courtesy U.S. National Science Foundation.

Queues work well for smaller groups discussing non-controversial topics. But when the energy level rises, or the headcount passes a dozen or so, disorder sometimes appears in the form of thread tangling.

A "thread" in a discussion is a collection of related contributions. In most discussions, although all contributions are related, some contributions are more closely connected than others. For instance, one thread might consist of several contributions rebutting one assertion, while another thread might offer support for an altogether different assertion.

Sometimes individual threads get fragmented, or tangled, because of the uncoordinated order of arrival in the queue. This thread tangling can lead to feelings of frustration, for several reasons.

Pseudo-plopping
"Plopping" is the systematic but polite ignoring of the contributions of one or more individuals. Their contributions, whatever they are, go "plop." Consequently, the people who are ignored can feel so alienated and bitter that they cease contributing.
Pseudo-plopping is what happens when a discussion's threads become so tangled that contributions seem to be ignored because they are forgotten or mislaid in the mess. The result is frustration, and possibly some of the same feelings as occur in plopping.
Information overload
People have a limited ability to remember chunks of information [Miller 1956]. The number of distinct chunks seems to be People lose track of the
conversation, or forget
some of what they
wanted to say
seven plus or minus two. Under stress, when angry, or amid interruptions or distractions, the limit is probably lower.
Trouble occurs when the limit is less than the number of contributions intervening between the time when a participant first enters the queue and when that participant finally speaks. People lose track of the conversation, or forget some of what they wanted to say. Some feel frustrated; some feel inadequate. They experience stress.
Defocusing
When three or more threads are active, the difficulty of keeping them all in focus overwhelms most people. Some have the experience of wanting to contribute to more than one thread.
When people who want to make multiple contributions to different threads finally do speak, they have to flip from one thread to the next. Sometimes, things get so confusing that they have to use notes. They forget some of what they wanted to say, they misspeak, or worse. Discourse quality degrades.

Thread tangling makes discussions disconnected and confusing. People feel stress. Destructive conflict is more likely to erupt. Thread tangling is bad news. Next time, we'll explore some techniques for dealing with thread tangling.  Next in this series Go to top Top  Next issue: Untangling Tangled Threads  Next Issue

[Miller 1956]
George A. Miller. "The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information." The Psychological Review, 1956, vol. 63, pp. 81-97. Back

101 Tips for Effective MeetingsDo you spendyour 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? rbrenmqcrpzmHaqobnDKsner@ChacHeWdKSKwOTlxqtAioCanyon.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.

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:

Thumbs downRecalcitrant Collaborators
Much of the work we do happens outside the context of a team. We collaborate with people in other departments, other divisions, and other companies. When these collaborators are reluctant, resistive, or recalcitrant, what can we do?
The Johari WindowAssumptions and the Johari Window: I
The roots of both creative and destructive conflict can often be traced to differing assumptions of the parties to the conflict. Working out these differences is a lot easier when we know what everyone's assumptions are.
The rabbit that went down the rabbit-holeOur Last Meeting Together
You can find lots of tips for making meetings more effective — many at my own Web site. Most are directed toward the chair, or the facilitator if you have one. Here are some suggestions for everybody.
Perceptual illusions resulting from reificationThe Reification Error and Performance Management
Just as real concrete objects have attributes, so do abstract concepts, or constructs. But attempting to measure the attributes of constructs as if they were the attributes of real objects is an example of the reification error. In performance management, committing this error leads to unexpected and unwanted results.
A bottlenose dolphinWacky Words of Wisdom: V
Adages, aphorisms, and "words of wisdom" are true often enough that we accept them as universal. They aren't. Here's Part V of some widely held beliefs that mislead us at work.

See also Personal, Team, and Organizational Effectiveness, Effective Meetings and Conflict Management for more related articles.

Forthcoming issues of Point Lookout

The end of the line for a railroad trackComing May 30: Chronic Peer Interrupters: I
When making contributions to meeting discussions, we're sometimes interrupted. Often, the interruption is beneficial and saves time. But some people constantly interrupt their peers or near peers, disrespectfully, in a pattern that compromises meeting outcomes. How can we deal with chronic peer interrupters? Available here and by RSS on May 30.
Mohandas K. Ghandi, in the 1930sAnd on June 6: Chronic Peer Interrupters: II
People use a variety of tactics when they're interrupted while making contributions in meetings. Some tactics work well, while others carry risks of their own. Here's Part II of a little survey of those tactics. Available here and by RSS on June 6.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenkoXtwTONrRjPKUgPner@ChacQmuyvvjadjxvqODaoCanyon.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:

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

Public seminars

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program. Here's a date for this program:

Technical Debt Management: Making the Business Case
This Technical Debt Management: Making the Business Caseprogram outlines the steps necessary for deploying a program for rational management of technical debt. For many organizations, adopting a program for rationally managing technical debt entails organizational change. And unlike some organizational changes, this one touches almost everyone in the organization, because technical debt isn't merely a technical problem. Technical debt manifests itself in technological assets, to be sure, but its causes are rarely isolated to the behavior and decisions of engineers. We can't resolve the problem of chronically excessive levels of technical debt by changing the behavior of engineers alone. Technical debt is the symptom, not the problem. In this program we outline the essential elements of an effective business case for adopting a rational technical debt management program. But this business case, unlike many business cases, cannot be captured in a document. We must make the case not only at the leadership level of the organization, but also at the level of the individual contributor. Everyone must understand. Everyone must contribute. We explore five issues that make technical debt so difficult to manage, and develop five guidelines for designing technical debt management strategies for the modern enterprise. Read more about this program. Here's a date for this program:

The Race to the South Pole: The Power of Agile Development
On 14The Race to the Pole: An Application of Agile Development 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 a date for this program:

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program. Here's a date for this program:

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy 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!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.