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
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.
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!
Your comments are welcomeWould you like to see your comments posted here? rbrenYqqeKrFLvzBJXHWNner@ChaczbzpRUAOBEdJRnrhoCanyon.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:
- The Hypothetical Trap
- Politicians know that answering hypothetical questions is dangerous, but it's equally dangerous for
managers and project managers to answer them in the project context. What's the problem? Why should
you be careful of the "What If?"
- Seven Ways to Get Nowhere
- Ever have the feeling that you're getting nowhere? You have the sense of movement, but you're making
no real progress towards the goal. How does this happen? What can you do about it?
- How to Foresee the Foreseeable: Preferences
- When people collaborate on complex projects, the most desirable work tends to go to those with highest
status. When people work alone, they tend to spend more time on the parts of the effort they enjoy.
In both cases, preferences rule. Preferences can lead us astray.
- How to Avoid Getting What You Want
- Why would you want to know how to avoid getting what you want? Well, suppose you had perfected ways
of avoiding getting what you want, but you weren't aware that you were doing it. This one's for you.
- The Risks of Too Many Projects: I
- Some organizations try to run too many development projects at once. Whether developing new offerings,
or working to improve the organization itself, taking on too many projects can defocus the organization
and depress performance.
Forthcoming issues of Point Lookout
- Coming July 26: Strategic Waiting
- Time can be a tool. Letting time pass can be a strategy for resolving problems or getting out of tight places. Waiting is an often-overlooked strategic option. Available here and by RSS on July 26.
- And on August 2: Linear Thinking Bias
- When assessing the validity of problem solutions, we regard them as more valid if their discovery stories are logical, than we would if they're less than logical. This can lead to erroneous assessments, because the discovery story is not the solution. Available here and by RSS on August 2.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenOgmTetczuJUarhQaner@ChacIYyFVngddFwdhJIwoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's a date for this
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 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, but to organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here's a date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- 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.