Virtual Communications: III

Here's Part III of my guidelines for communications in virtual teams. See "Virtual Communications: II," Point Lookout for February 2, 2005, for more.

Don't give the time or date in voicemail

Most systems already provide the day, date, and time for messages. Why duplicate it? And if you're in a different day and time yourself, you could just confuse the recipient.

Give your phone number twice

For voicemail messages, supply your phone number not only near the beginning, but also at the end.

If using a desk or wall phone, press the button to hang up

Replacing the handset to hang up creates a clattering sound that can be irritating in voicemail.

Eating, drinking, and chewing gum are no-nos on the phone

Whether live or in voicemail, avoid these activities. Even when you're muted, you never know when you'll need to speak.

Sit up straight or stand when you're on the phone

Sit up straight
when you're on the phone.
You need the full power
and nuance of your voice.

Slouching or lying down interferes with full use of your lungs and diaphragm. You need the full power and nuance of your voice.

Learn how to use your voicemail system

Learn how to skip, skip-with-erase, move to mailbox, reply-immediate, pause, repeat, transfer to email, forward, forward with preface, forward to list, sort by priority, and whatever else your system offers.

Learn the remote commands too

If you call into your office system to pick up messages, learn the most useful commands. And carry them on a wallet card.

Customize your outgoing message

If you know you'll be returning at a specific time, record an outgoing message that tells callers when to call back. This can really cut down on your voicemail.

Consider calling someone's voicemail directly

Often, you don't really need to speak to the recipient live. If a voicemail will do, call voicemail directly.

Suspend interpretation of silences

If someone doesn't respond to a message — email or voice — check whether the message was received. Going ballistic is usually a bad idea, especially when based on a misinterpretation of silence.

Always confirm — don't rely on silence

Never leave a message of the form "I'll let you know if X condition is satisfied, otherwise execute Y." Always confirm either way, because messages don't always arrive.

Slow down your "offense" response

In face-to-face communications, we use body language, facial expression, and tone of voice to adjust our communications and our interpretations, and this keeps us out of trouble. By email and phone, where these adjustments are problematic or impossible, we're more likely to offend and to feel offended. Slow down and ask for elaboration. Breathe more.

Most important, express appreciations verbally, publicly, and often. In person, we smile, we nod, we backslap, and any number of other things that express approval nonverbally. Remotely, these gestures are unavailable to us, so when we want to encourage each other, or express approval, we have to say things verbally that seem unnatural, artificial, or forced. It takes practice. Get started today.  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:

Mastering Meeting Madness

If you lead an organization, and people are mired in meeting madness, you can end it. Here are a few tips that can free everyone to finally get some work done.

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.

Management Debt: II

As with technical debt, we incur management debt when we make choices that carry with them recurring costs. How can we quantify management debt?

The Retrospective Funding Problem

If your organization regularly conducts project retrospectives, you're among the very fortunate. Many organizations don't. But even among those that do, retrospectives are often underfunded, conducted by amateurs, or too short. Often, key people "couldn't make it." We can do better than this. What's stopping us?

Overconfidence at Work

Confidence in our judgments and ourselves is essential to success. Confidence misplaced — overconfidence — leads to trouble and failure. Understanding the causes and consequences of overconfidence can be most useful.

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

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