Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 8, Issue 15;   April 9, 2008: Remote Facilitation in Synchronous Contexts: III

Remote Facilitation in Synchronous Contexts: III

by

Facilitators of synchronous distributed meetings (meetings that occur in real time, via telephone or video) can make life much easier for everyone by taking steps before the meeting starts. Here's Part III of a little catalog of suggestions for remote facilitators.
The Samuel Morse Telegraph Receiver

The Samuel Morse Telegraph Receiver that was used to receive the message, "What hath God wrought," during the demonstration to Congress in 1844. Over the remainder of the nineteenth century, the equipment improved dramatically, but the demand for bandwidth grew even more dramatically. To limit costs, senders of telegrams turned to a vast array of so-called telegraph codebooks, which contained code words that stood for often-used phrases or sentences. Prior to sending messages, people would agree to use a specific code, and thereby save money and time in message transmission. For instance, "The Nautical Telegraph Code Book and Postal Guide," edited by Capt. D.H. Bernard (London, 1908), defines the code word seclusion, to mean, "Sorry to say ship caught fire last night — serious damage."

Fifty years from now, people will write about our use of telephony for distributed meetings. They'll describe the artifices we use to resolve speaker identity, recognize speakers, and manage interruptions. And these devices will seem as quaint to people in the future, as the telegraph codebooks seem to us now. Photo courtesy Smithsonian National Museum of American History.

We cannot anticipate every problem facilitators might encounter in synchronous distributed meetings, but some are fairly predictable. And we can manage some of these problems more easily either by limiting their incidence, or by establishing protocols for them in advance. Here are three examples.

Identifying the speaker
In face-to-face (F2F) meetings, identifying the speaker is usually easy. We can either see the speaker, or we can recognize the voice, or tell which direction it's coming from, even if the facilitator recognizes the speaker by inaudible means such as a slight gesture.
In the distributed context, especially audio-only, identification can be problematic. To address the difficulty, the facilitator can recognize the speaker by name, and the speaker can begin by stating his or her name. And before the meeting starts, we can make available a podcast with attendees introducing themselves in their own voices.
Managing complex technologies
To support their telemeetings, some groups use complex technologies that go beyond telephone or videoconferencing. Tools for sharing drawing spaces, displaying slide presentations, and even manipulating physical objects all require special skills.
Although these technologies are at the frontier of remote facilitation, some useful practices have emerged. First, ensure in advance that all sites have operative installations. Pushing ahead when it's known that some sites don't have functioning installations risks corrupting meeting deliverables. Second, ensure that any participants who must use the technology have had adequate training. Third, have technical support staff standing by during the meeting for advice or repair if necessary. Finally, be prepared to halt the meeting and reschedule it if essential technology doesn't function correctly.
Dealing with interrupters
In F2F meetings, participants
who interrupt others create
problems, but facilitators
can handle them
In F2F meetings, participants who interrupt others create problems, but facilitators can handle them fairly easily. And when interruptions do occur, everyone can usually sort out what was said. In distributed meetings, especially over the telephone, we can't always identify the interrupter and we often can't sort out what was said.
"Zero tolerance" for interruptions is probably an impossible goal, but you can adopt practices that reduce their incidence. In advance of the meeting, establish a norm that prohibits routine interruptions, and establish a protocol for emergency interruptions. Circulate news flashes before the meeting or as a first agenda item to reduce the need for people to inject news during discussions. Interruptions that come about during heated debate are another matter; deal with repeat offenders privately.

Often, meeting size itself is a difficult challenge, because we don't want to risk offending people by excluding them. Making available a podcast of the meeting, and offering "podcast attendance" as an option for some people in advance, might tempt a few to attend by podcast. Unfortunately, as the facilitator, podcast attendance is not an option for you. First in this series  Go to top Top  Next issue: Organizational Loss: Searching Behavior  Next Issue

303 Tips for Virtual and Global TeamsIs your organization a participant in one or more global teams? Are you the owner/sponsor of a global team? Are you managing a global team? Is everything going well, or at least as well as any project goes? Probably not. Many of the troubles people encounter are traceable to the obstacles global teams face when building working professional relationships from afar. Read 303 Tips for Virtual and Global Teams to learn how to make your global and distributed teams sing. Order Now!

For an examination of some issues that arise in synchronous distributed meetings, see "Remote Facilitation in Synchronous Contexts: I," Point Lookout for March 26, 2008. For suggestions for facilitating highly charged distributed meetings, see "Remote Facilitation in Synchronous Contexts: II," Point Lookout for April 2, 2008.

Your comments are welcome

Would you like to see your comments posted here? rbrenBzabwhFGnZcQykGCner@ChaclLvFNKklSKQHJKvMoCanyon.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:

A forest glenGames for Meetings: I
We spend a lot of time and emotional energy in meetings, much of it engaged in any of dozens of ritualized games. Here's Part I of a little catalog of some of our favorites, and what we can do about them.
The Gatun Locks of the Panama Canal, showing their guide wallsIn the Groove
Under stress, we sometimes make choices that we later regret. And we wonder, "Will I ever learn?" Fortunately, the problem usually isn't a failure to learn. Changing just takes practice.
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 Johari WindowAssumptions and the Johari Window: 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 bark of the American SycamoreMitigating Outsourcing Risks: II
Outsourcing internal processes exposes the organization to a special class of risks that are peculiar to the outsourcing relationship. Here is Part II of a discussion of what some of those risks are and what can we do about them.

See also Personal, Team, and Organizational Effectiveness, Effective Meetings, Project Management and Virtual and Global Teams for more related articles.

Forthcoming issues of Point Lookout

Jeffrey Skilling, in a mug shot taken in 2004 by the United States Marshals ServiceComing May 23: Narcissistic Behavior at Work: IX
An arrogant demeanor is widely viewed as a hallmark of the narcissist. But truly narcissistic arrogance is off the charts. It's something beyond the merely annoying arrogance of a sometimes-obnoxious individual. What is narcissistic arrogance and how can we cope with it? Available here and by RSS on May 23.
The end of the line for a railroad trackAnd on 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.

Coaching services

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

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.

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.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.