
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 issue in this series
Top
Next Issue
Is 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? rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.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:
Snapshots of Squirming Subjects
- Today we use data as a management tool. We store, recall, and process data about our operations to help
us manage resources and processes. But this kind of management data is often scattered, out of date,
or just plain incorrect, and taking a snapshot doesn't work. There is a better way.
Retention
- When the job market eases for job seekers, we often see increases in job shifting, as people who've
been biding their time make the jump. Typically, they're the people we most want to keep. How can we
reduce this source of turnover?
The Perils of Piecemeal Analysis: Content
- A team member proposes a solution to the latest show-stopping near-disaster. After extended discussion,
the team decides whether or not to pursue the idea. It's a costly approach, because too often it leads
us to reject unnecessarily some perfectly sound proposals, and to accept others we shouldn't have.
Logically Illogical
- Discussions in meetings and in written media can get long and complex. When a chain of reasoning gets
long enough, we sometimes make fundamental errors of logic, especially when we're under time pressure.
Here are just a few.
Goodhart's Law and Reification
- Goodhart's Law, applied to organizations, is an observation about managing by metrics. When we make
known the goals for our metrics, we risk having the metrics lose their ability to measure. The risk
is elevated when we try to "measure" abstractions.
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
Coming May 14: Working with the Overconfident
- A cognitive bias known as the Overconfidence Effect causes us to overestimate the reliability of our judgments. Decisions we make based on those judgments are therefore suspect. But there are steps we can take to make our confidence levels more realistic, and thus make our decisions more reliable. Available here and by RSS on May 14.
And on May 21: Mismanaging Project Managers
- Most organizations hold project managers accountable for project performance. But they don't grant those project managers control of needed resources. Nor do they hold project sponsors or other senior managers accountable for the consequences of their actions when they interfere with project work. Here's a catalog of behaviors worth looking at. Available here and by RSS on May 21.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.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
rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
