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 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 welcomeWould you like to see your comments posted here? rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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.
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.
More articles on Personal, Team, and Organizational Effectiveness:
- When Your Boss Attacks Your Self-Esteem
- Your boss's comments about your work can make your day — or break it. When you experience a comment
as negative or hurtful, you might become angry, defensive, withdrawn, or even shut down. When that happens,
you're not at your best. What can you do if your boss seems intent on making every day a misery?
- Dangerous Phrases
- I recently upgraded my email program to a new version that "monitors messages for offensive text."
It hasn't worked out well. But the whole affair got me to think about everyday phrases that do tend
to set people off. Here's a little catalog.
- False Summits: II
- When climbers encounter "false summits," hope of an early end to the climb comes to an end.
The psychological effects can threaten the morale and even the safety of the climbing party. So it is
in project work.
- Paradoxical Policies: II
- Because projects are inherently unique, constructing general organizational policies affecting projects
is difficult. The urge to treat projects as if they were operations compounds the difficulty. Here's
a collection of policies for projects that would be funny if they weren't real.
- Wacky Words of Wisdom: VI
- Adages, aphorisms, and "words of wisdom" seem valid often enough that we accept them as universal
and permanent. Most aren't. Here's Part VI of a collection of widely held beliefs that can be misleading
Forthcoming issues of Point Lookout
- Coming January 22: Disjoint Awareness: Bias
- Some cognitive biases can cause people in collaborations to have inaccurate understandings of what each other is doing. Confirmation bias and self-serving bias are two examples of cognitive biases that can contribute to disjoint awareness in some situations. Available here and by RSS on January 22.
- And on January 29: Higher-Velocity Problem Definition
- Typical approaches to shortening time-to-market for new products usually involve accelerating problem solving. Accelerating problem definition can also help. Available here and by RSS on January 29.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info
- The Power Affect: How We Express Our Personal Power
Many people 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.