Virtual Communications: II

Ed picked Katrina's number from his cell phone menu, slid his coat just a bit off his right shoulder, stuck the phone between his shoulder and his ear, froze for a moment with his right arm halfway out of his coat sleeve, and listened. "Good," he said aloud to himself, "Ringing. Maybe she's in."

He listened to the ringing as he slid his right arm out of his coat, then his left. He threw the coat on the hard hotel bed and sat down on the desk chair. As he began untying his left shoe, Katrina's voice came on the line.

It was her outgoing message. She gave her name and said, "Press star to skip this message." Ed pressed star, thinking, 'Thank you, Katrina.' He'd heard her message thousands of times, but he could never remember how to skip her message.

When Katrina recorded her outgoing message, she gave a gift to all of her colleagues by telling them how to skip her message. For repeat callers like Ed, it saves a few seconds every time. It adds up, and it can be a wonderful thing when he's rushed, or at the end of a long day. Little niceties like that can make the difference between a high-performance team and one that struggles to survive.

Here's Part II of my guidelines for communications within virtual teams. See "Virtual Communications: I," Point Lookout for January 26, 2005, and "Virtual Communications: III," Point Lookout for February 9, 2005, for more.

Use Call Waiting only with Caller ID

Interrupting a call just to find out who else is calling is a destructive practice. Get a service called "Caller ID with Name on Call Waiting," which lets you see who's calling without interrupting the current call. Even with this service, interrupt a call only for emergencies or when the second caller calls a second time.

Think "inbox" when leaving voicemail

For voicemail, follow the format we use for email: first give your name, your full phone number, the topic, and the priority, and then give the body of the message. It's a courtesy to the listener.

Speak slowly in voicemail

Speak clearly. If you're calling from a noisy environment, such as an airport, try to find a quiet place to make your call. Slow down even more when you say your phone number or email address.

Don't make up voicemail messages on the fly

Be realistic — you'll probably have to leave a message when you call. Be prepared to do so.

Leave only simple voicemail messages

Complex voicemail messages are hard to follow. The recipient almost always has to write them down. If possible, send complex messages by email. Thirty seconds is the practical maximum, especially if the recipient gets lots of voicemail.

Say goodbye only once

It's amazing how many people say multiple goodbyes. One will do the job.

How many voicemail messages will your team send this year? Think about how much time you can save, and how much confusion you can avoid, if your team follows these guidelines. Just don't try to explain them in voicemail.  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!

Your comments are welcome

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:

What Haven't I Told You?

When a project team hits a speed bump, it often learns that it had all the information it needed to avoid the problem, sometimes months in advance of uncovering it. Here's a technique for discovering this kind of knowledge more systematically.

Organizing a Barn Raising

Once you find a task that you can tackle as a "barn raising," your work is just beginning. Planning and organizing the work is in many ways the hard part.

When Stress Strikes

Most of what we know about person-to-person communication applies when levels of stress are low. But when stress is high, as it is in emergencies, we're more likely to make mistakes. Knowing those mistakes in advance can be helpful in avoiding them.

How to Reject Expert Opinion: II

When groups of decision makers confront complex problems, and they receive opinions from recognized experts, those opinions sometimes conflict with the group's own preferences. What tactics do groups use to reject the opinions of people with relevant expertise?

How to Deal with Holding Back

When group members voluntarily restrict their contributions to group efforts, group success is threatened and high performance becomes impossible. How can we reduce the incidence of holding back?

See also Personal, Team, and Organizational Effectiveness, Effective Communication at Work and Virtual and Global Teams for more related articles.

Forthcoming issues of Point Lookout

Coming April 24: Antipatterns for Time-Constrained Communication: 1

Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.

And on May 1: Antipatterns for Time-Constrained Communication: 2

Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 2 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.

Coaching services

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