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.

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:

The True Costs of Cubicles

Although cubicles do provide facility cost savings compared with walled offices, they do so at the price of product development delays and increased product development costs. Decisions of facilities planners can have dramatic project schedule impact.

Organizational Loss: Searching Behavior

When organizations suffer painful losses, their responses can sometimes be destructive, further harming the organization and its people. Here are some typical patterns of destructive responses to organizational loss.

Hyper-Super-Overwork

The prevalence of overwork has increased with the depth of the global recession, in part because employers are demanding more, and in part because many must now work longer hours to make ends a little closer to meeting. Overwork is dangerous. Here are some suggestions for dealing with 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.

Paradoxical Policies: II

Because projects are inherently unique, constructing general organizational policies affecting projects is difficult. The urge to treat projects as if they were operations compounds the difficulty. Here's a collection of policies for projects that would be funny if they weren't real.

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 October 23: Power Distance and Teams

One of the attributes of team cultures is something called power distance, which is a measure of the overall comfort people have with inequality in the distribution of power. Power distance can determine how well a team performs when executing high-risk projects. Available here and by RSS on October 23.

And on October 30: Power Distance and Risk

Managing or responding to project risks is much easier when team culture encourages people to report problems and question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk. Available here and by RSS on October 30.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Race to the South Pole: Lessons in Leadership

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. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.

Here's a date for this program:

• Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio 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.

• A recording of a program presented June 29, 2017, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.