CommunicationsEffective Project Communications

Click here to RSVP for the webinar on this topic on Thursday August 20th from 2-2:30pm (eastern)

Communication is critical when working on a project, but how do we best gauge how much is enough? Too much? In person or in writing? By groups or individuals?  Routinely scheduled or ad hoc? The answer depends on the size and nature of the project, the preference of the team, and organizational requirements. And all of this is determined as you create your communication plan.

Your project communication plan can be as simple or complex as you need. It’s purpose is to document how various information within a project will be communicated. Some common methods of communication you’ll see in communication plans are:

Project Reports: Probably the most important communication, reports are usually listed specifically by name. You’ll also want to document the recipients, the sender, and the schedule of delivery. Oftentimes we’ll set variances for reports as well. For example, a standard budget report might suffice, unless the budget exceed 10% of the plan, then perhaps we would want to also include a detailed budget report, and escalate the recipients.

Meeting Notes: You’ll want to determine how to best distribute meeting notes. Options might include saving a document to a shared folder, sending and email, or making an entry in a SharePoint site.

Contact Information: If you are working with a diverse team, especially those outside your organization, it’s great to get everyone’s contact information in one place.

Meeting plan: I like to document a plan for scheduled meetings in my communication plan. I’ll list who should attend, the nature of the meeting, and the options for participation. For example:

Meeting Cadence Attendees Options for attending
Working level meetings Weekly or as needed TBD In person or phone
Status meetings Bi-weekly Resources with active and upcoming tasks In person or Skype call
Project review Monthly Entire project team In person


Go to resources: I also like to list resources that are specifically responsible for certain things that might impact my project. For example, who should we talk to if we need elevated access rights? What about after hours supports, is there anyone available for that?

I typically like to have some conversations during the beginning of the project to determine what would work best, and then go over that plan before the project starts (or during if need be). Your communication plan doesn’t have to be formal. It’s purpose is to help document who needs to know what and when. Sometimes it’s as simple as emailing meeting notes and providing a weekly report. And sometimes it’ll be more involved. The most important thing to remember about communication plans is to customize them to meet the needs of the project. You don’t want to over communicate – your team will start to ignore your emails if they receive 50 a day. But not communicating enough can impact the project. So have some conversations about communications needs and preferences and you’ll set yourself up for an effective, well informed project team.

Join us on August 20th for the Project Management webinar on Project Communications. We’ll look at some of the reports available in MS Project and Project Web App and discuss getting the right information to each person on the project team.