To yield expected results, a distributed project team must first speak the same language when it comes to communications.
With that in mind, I developed a basic set of email communications rules called the Project Communication Decalogue. I require everyone on my team to adhere to it when emailing each other, and I introduce it the first time I meet with a new team or member. When everyone is on the same page, it makes for leaner, cleaner communications.
- Don't be cute in the subject line. Attract the attention of the recipient using powerful, descriptive language in subject lines. Include a call for action when needed, including statements like: URGENT, FOR YOUR IMMEDIATE ATTENTION or ESCALATION REQUIRED.
- Limit the distribution list. Include only the interested parties in the messages. Beware the "Reply All" button.
- Start fresh. Remove unnecessary email trails -- for example, when the messages start to deviate from the original topic. Better yet, when possible, create a new message to continue the discussion.
- Manage response expectations. Let your team members know the reason for a delay, in the event you are not able to take immediate action on a request or conversation.
- Filter and follow the thread. If the number of messages on a topic starts to get out of hand, sort them by subject or conversation. Return to the first of the sequence to find clarity on the issue at hand. Then, scan the rest of the message's trail to determine what requires attention and action.
- Do not engage in email battles. Avoid confrontation online. It is just not productive and creates clutter in your inbox. If you spend more than 10 minutes crafting an email, you are better off scheduling a meeting or call with your counterpart to address the problem in an actual conversation.
- Turn on auto-reply. As a courtesy to your teammates, enable the "out-of-the-office" feature. Specify your length of absence from the office and who will be covering while you are out.
- Make thorough meeting invitations via email. List the agenda and attach any documents that will be reviewed during a conference call. Do not send documents minutes before the call, expecting that attendees will be online.
- Always include the meeting location. In the location box of your calendar invite, include the meeting room data and any pertinent communication information, such as the conference bridge number and PIN.
- Check the availability of meeting participants. As many email clients allow you to check a participant's availability, do not send calendar invitations knowing that one or more participants are unavailable. This will reduce email traffic.
From experience, the adoption of these rules takes a few weeks. But once you get buy-in from all team members, email communications become a smoother process, freeing up time to focus on much more important project tasks.
What are your basic email communication rules? How do you get your project team to speak the same language via email?
by Conrado Morlan
on: April 05, 2013 10:08 AM |