Table of Contents |
Emails are flexible communication methods used for announcements, instruction, or project direction. Emails should be brief. If you find yourself writing a long email, perhaps the information would be better communicated through another method.
It is important to be clear and concise when communicating with project stakeholders. Their time is valuable so deliver the information they need to recognize issues and make decisions.
However, email has limitations. Emails are not the best method for large discussions, so the project manager should be careful with questions when using email, especially when asking open-ended questions at the beginning of an email.
If sensitive issues with an individual must be communicated, email may not be best due to a common misinterpretation of emotional tone.
Be careful copying too many people on an email using the CC (Carbon Copy) or BCC (Blind Carbon Copy) functions. Information in the email should apply to everyone on the list. If your stakeholders and team members receive too many emails, they may begin to ignore future communication via email.
Presentations should be held when a large amount of information needs to be conveyed, and the project manager needs more control over the flow of that information.
Though question and answer sessions occur with presentations, this is primarily a method for the presenter to pass information to the audience, not the other way around.
If discussions are necessary, then meetings are a better medium for communication, especially if the issue or decision being discussed impacts more than one stakeholder or team member.
If only one stakeholder or team member is impacted, then perhaps a one-to-one discussion is the best method, either on the phone or in person. This should also be used when the information being discussed is confidential or private.
If a meeting is more appropriate than an email, it is the project manager's responsibility to manage the meeting and can follow this sequence when organizing a meeting:
Documentation, either printed or online, should be used when planning and documenting project actions. It's critical to record the history of a project in case questions arise later about decisions made earlier in a project. Documentation is also used when information is accessed often throughout a project, such as with procedures, checklists, or frequently asked questions.
Source: THIS WORK IS ADAPTED BY SOPHIA AUTHOR JEFF CARROLL.