Virtual Communications: I

Katrina picked up the pencil and punched Ed's number. The circuit completed and she could hear the line ring. It rang again. She started tapping the pencil on her desk. The line rang again. 'Still not there,' she thought, tapping the pencil. 'Where is he?'

Then Ed's voice came on the line, but it was his outgoing message. Katrina thought for a moment, and hung up. "Damn," she said out loud, to nobody.

Frustrated as she might be, Katrina has just done something smart — rather than leave Ed yet another message, she decided to just hang up, saving both Ed and herself some time.

Virtual teams depend on effective telephone and email communications, and that effectiveness has both individual and team components. Here's Part I of some guidelines for virtual team communications. See "Virtual Communications: II," Point Lookout for February 2, 2005, for more.

Have regular check-ins

If you lead or manage the team, check in with each team member regularly. Depending on the nature of the work, you might check in daily, or two or three times a week — less often than that risks disconnection.

Make appointments

Communicating within
a virtual team
as if you were
co-located almost
never works

Making appointments minimizes phone tag, which is expensive in terms of stress, frustration, and time spent. When you want to talk with someone, make an appointment, possibly by email or by text message.

Keep your appointments

Running a little late when someone is waiting outside your office does hurt, but not nearly as much as running late for a phone conversation. When you're late for a phone appointment, the caller often has less idea what's happening or when you'll be available.

If you're running late, take time out in advance — if you can — to advise your next appointment that you're late. Rescheduling is best.

Agree on message response times

Adopt a standard of reasonableness for the elapsed time to respond to email or phone messages. A rough rule of thumb: respond in about half the time you thought was reasonable outside of the remote management context.

Use meta-responses

If you can't return a message promptly, send a message saying so. If you can explain why, all the better, but at least let your partner know that you're aware of the delay, and estimate when you can respond.

Define a three-level priority scale for messages

Green messages (good news or bad) are nonurgent, yellow is possibly urgent, and red messages are urgent. Use this scale for email and voicemail, taking care never to inflate a priority just to get attention.

Agree that nonresponse is a performance issue

Agree that failure to respond to (or at least to acknowledge) a message within a "reasonable" time could be a serious performance issue. Clearly define the kinds of circumstances that could excuse the failure to respond.

I'd like to continue, but we're out of time for this week. Let's continue at the same time next week.  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!

Reader Comments

Chris Riemer (www.knowledgestreet.com)

Your advice is generally nontechnological, but I thought I'd mention something that was a great help in improving the efficiency of a virtual team I managed in the past: webcams.

We already had a network backbone, and I spent a few bucks to buy a webcam for each location. Using only Microsoft's NetMeeting, it gave me a chance to see the folks who were many miles away, and that was an opportunity to notice a new hair cut, or see a smile, or share a picture of the dog. It made us feel much more in touch than the telephone alone. I was famous for drawing ideas on my white board, so this also let me communicate in the way I like to, even if the white board was pretty hard to see with a webcam.

Your comments are welcome

Would you like to see your comments posted here? rbrenZLkFdSHmlHvCaSsuner@ChacbnsTPttsdDaRAswloCanyon.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.

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:

When We Need a Little Help

Sometimes we get in over our heads — too much work, work we don't understand, or even complex politics. We can ask for help, but we often forget that we can. Even when we remember, we sometimes hold back. Why is asking for help, or remembering that we can ask, so difficult? How can we make it easier?

Mudfights

When we steer the discussion away from issues to attack the credibility, motives, or character of our debate partners, we often resort to a technique known as the ad hominem attack. It's unfair, it's unethical, and it leads to bad, expensive decisions that we'll probably regret.

Wacky Words of Wisdom: II

Words of wisdom are so often helpful that many of them have solidified into easily remembered capsules. And that's where the trouble begins. We remember them too easily and we apply them too liberally. Here's Part II of a collection of often-misapplied words of wisdom.

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?

Red Flags: II

When we find clear evidence of serious problems in a project or other collaboration, we sometimes realize that we had overlooked several "red flags" that had foretold trouble. In this Part II of our review of red flags, we consider communication patterns that are useful indicators of future problems.

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 February 8: Kerfuffles That Seem Like Something More

Much of what we regard as political conflict is a series of squabbles commonly called kerfuffles. They captivate us while they're underway, but after a month or two they're forgotten. Why do they happen? Why do they persist? Available here and by RSS on February 8.

And on February 15: Four Razors for Organizational Behavior

Deviant organizational behavior can harm the people and the organization. In choosing responses, we consider what drives the perpetrators. Considering Malice, Incompetence, Ignorance, and Greed, we can devise four guidelines for making these choices. Available here and by RSS on February 15.

Coaching services

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