Telephone and videoconferences are the next best thing to being there. Unfortunately second place is pretty far back in that race. For routine meetings about routine topics, and for highly functional teams, even though distributed meetings are a bit cumbersome, their pace is tolerable.
But for highly charged discussions, or for teams caught in toxic conflict, or when the pressure rises, the limitations of distributed meetings become clear. Facilitators skilled in dealing with these limitations can work around them, but the workarounds require methods that would seem awkward in the face-to-face (F2F) context. Here are some examples.
- Collision avoidance and resolution
- In face-to-face meetings a "collision" is two or more people attempting to speak at once. Most facilitators manage this problem well by asserting and maintaining control of the recognition process, using the tools of personal presence. In virtual or distributed meetings, most of those tools are limited, work differently, or are unavailable.
- As facilitator, explain at the outset that you'll recognize speakers in turn. In videoconferences, hand signals might suffice for speakers seeking recognition, and signals can be given at any time. In telephone conferences, once open discussion begins, the audible request is the only means available. Since such requests might interrupt the speaker, open the floor for requests for time only during a "time-request window" between speakers. Use a brief protocol for requesting the floor — something like "Rick wants time." You'll also want a protocol for withdrawing a request — something like "Rick says 'Never mind.'" Describe also a high priority interrupt protocol to be used only by those who have critical information that will shorten the discussion — something like "Rick has a point of information."
- Queue management
- In virtual or distributed meetings,
most of the facilitator's
customary tools are limited,
or are unavailable
- In both distributed and F2F meetings, a queue can develop in open discussion, as people request time. In F2F meetings some facilitators maintain the queue on a flip chart or whiteboard that all can see. That might also work well in videoconferences or in distributed meetings with shared writing space.
- In audio-only distributed meetings, repeat the queue aloud at the end of each time-request window.
- Recognition is the process by which the facilitator designates the next speaker. In F2F meetings a nod or a smile suffices, with an optional accompanying verbal cue, such as the speaker's name.
- In the distributed context, the verbal cue is required. For safety, repeat it. When two people have identical or similar names, try to remove the ambiguity — perhaps referring to their sites or roles. Avoid disambiguating by means of personal attributes — even positive attributes — because of the risk of offense to the other person of the same name. Bad example: "Next: the smart Rick."
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 making remote facilitation easier using protocols defined for everyone in advance, see "Remote Facilitation in Synchronous Contexts: III," Point Lookout for April 9, 2008.
Your comments are welcomeWould you like to see your comments posted here? rbrenjaluJdNHMzxhsGFmner@ChacfaoXNyolYMlURJkpoCanyon.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:
- Some Costs of COTS
- As a way of managing risk, we sometimes steer our organizations towards commercial off-the-shelf (COTS)
components, methodologies, designs, and processes. But to gain a competitive edge, we need creative
- Problem-Solving Ambassadors
- In dispersed teams, we often hold meetings to which we send delegations to work out issues of mutual
interest. These working sessions are a mix of problem solving and negotiation. People who are masters
of both are problem-solving ambassadors, and they're especially valuable to dispersed or global teams.
- We Are All People
- When a team works to solve a problem, it is the people of that team who do the work. Remembering that
we're all people — and all different people — is an important key to success.
- Virtual Clutter: I
- With some Web searching, you can find abundant advice for decluttering your home or office. And people
are even thinking about decluttering email inboxes. But the problem of clutter is far more widespread.
- Heart with Mind
- We say people have "heart" when they continue to pursue a goal despite obstacles that would
discourage almost everyone. We say that people are stubborn when they continue to pursue a goal that
we regard as unachievable. What are our choices when achieving the goal is difficult?
Forthcoming issues of Point Lookout
- Coming 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.
- And 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.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenFwNYnzqJElGbXLVBner@ChacAlZiOeMaXhOrWIkDoCanyon.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, 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
- Technical Debt Management: Making the Business Case
- This program
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:
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield,
Illinois 62701: June 12,
Monthly Meeting, Central
Illinois Chapter of the Project Management Institute. Register now.
- Wyndham Springfield City Centre, 700 East Adams Street, Springfield, Illinois 62701: June 12, Monthly Meeting, Central Illinois Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: The Power of Agile Development
- 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. 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:
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227:
Monthly Meeting, Cincinnati
chapter of the International Institute of Business Analysis. Register now.
- Fifth Third Bank, 5717 Madison Road, Cincinnati, OH 45227: July 17, Monthly Meeting, Cincinnati chapter of the International Institute of Business Analysis. 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.