Project Management guide · Risk, quality and control
Project Communication Management: Process and Best Practice
Project communication management is the process of making sure the right people receive the right information, in the right format, at the right time. It covers planning what to communicate, sharing it, and checking that it has been understood and acted on.
Key takeaways
- Communication management covers planning, delivering and monitoring project information.
- Tailor message, method and frequency to each audience.
- Channels grow fast: n(n - 1) / 2.
- Always check that messages are understood and adjust the plan.
Why communication management matters
Many project problems, such as surprised sponsors, duplicated work and disputed scope, come from poor communication rather than poor technical work. Good communication builds trust, speeds up decisions and makes risks and issues visible while they are still easy to fix.
- Keeps stakeholders informed and engaged.
- Supports timely decisions by the sponsor and governance boards.
- Reduces misunderstanding about scope, priorities and responsibilities.
- Creates a record of decisions and agreements.
The three core processes
The PMBOK Guide sixth edition describes communication management in three processes. They form a simple cycle that repeats throughout the project.
| Process | What happens | Key output |
|---|---|---|
| Plan communications management | Analyse stakeholder needs and decide who gets what, when and how | Communication plan |
| Manage communications | Create, distribute, store and retrieve project information | Reports, presentations, meeting notes |
| Monitor communications | Check that communication is working and adjust the plan | Feedback, updates to the plan |
Communication methods and channels
| Method | Description | Examples | Best for |
|---|---|---|---|
| Interactive | Two-way, real-time exchange | Meetings, calls, video, workshops | Decisions, sensitive topics, resolving conflict |
| Push | Sent to specific people | Email, status reports, newsletters | Regular updates people must receive |
| Pull | Stored for people to access when needed | Intranet, shared drive, project tool dashboards | Reference material and large audiences |
The number of potential communication channels grows quickly with team size. The formula is n(n - 1) / 2, where n is the number of people.
- 5 people: 5 x 4 / 2 = 10 channels.
- 10 people: 10 x 9 / 2 = 45 channels.
- Adding 2 people to a team of 10 gives 12 x 11 / 2 = 66 channels, an increase of 21.
How to manage project communication step by step
- Identify stakeholders and analyse their interest, influence and information needs, for example with a RACI matrix.
- Agree objectives for communication: inform, consult, gain approval or build support.
- Choose methods and frequency for each audience, matching detail to the reader.
- Write the communication plan and agree it with the sponsor.
- Deliver consistently, using templates so reports are quick to read.
- Gather feedback through check-ins and short surveys, and watch for signs of confusion.
- Adjust the plan as stakeholders, phases and risks change.
Worked example
A 9-month ERP rollout has a steering committee, 4 department heads, a 12-person project team, an external supplier and 600 end users. The project manager tailors communication to each group.
| Audience | Need | Method | Frequency |
|---|---|---|---|
| Steering committee | Progress, key risks, decisions needed | Meeting plus one-page RAG report | Monthly |
| Department heads | Impact on their teams, readiness actions | Briefing call | Fortnightly |
| Project team | Tasks, blockers, priorities | Stand-up and team board | Daily |
| Supplier | Deliverables, issues, acceptance | Joint progress meeting | Weekly |
| End users | What is changing, when, training dates | Newsletter and intranet page | Monthly, weekly near go-live |
Three months in, feedback shows end users are not reading the newsletter. The project manager adds short team-meeting briefings delivered by department heads, and readiness survey scores improve. This is the monitor step in action.
Common mistakes and tips
- One message for everyone: executives need decisions and exceptions; teams need detail.
- Reporting activity, not outcomes: say what has changed and what you need, not just what was done.
- Hiding bad news: raise problems early, with options.
- No feedback loop: sending is not the same as communicating. Check understanding.
- Too many channels: agree where decisions and documents live, for example one project management tool.
Free templates for this topic
Frequently asked questions
What is project communication management?
The planning, delivery and monitoring of project information so that stakeholders receive what they need, when they need it, in a useful format.
What are the processes of communication management?
In the PMBOK Guide sixth edition: plan communications management, manage communications and monitor communications.
How do you calculate communication channels in communication management?
Use n(n - 1) / 2, where n is the number of people. A team of 8 has 28 channels.
What is the difference between push and pull communication in project communication management?
Push communication is sent to specific recipients, such as an email. Pull communication is stored for people to access themselves, such as an intranet page.
What is interactive communication in communication management?
Real-time, two-way exchange such as meetings, calls and workshops. It is best for decisions and complex or sensitive topics.
How much of a project manager's time goes on communication management?
A large share. Most of a project manager's work involves meetings, reporting, negotiating and coordinating with people.
How does a communication plan support communication management?
It is the main output of planning communication management: a document that sets out who needs what information, why, how and how often, and who is responsible for providing it.
How should communication management handle senior stakeholders?
Keep it short, lead with status and decisions needed, focus on exceptions and risks, and follow an agreed reporting rhythm.
What barriers does project communication management need to overcome?
Jargon, information overload, time zones, language differences, unclear ownership and too many tools or channels.
How do you know if project communication management is working?
Ask for feedback, check whether decisions are made on time, and watch for repeated questions, surprises or rework caused by misunderstanding.
What role does the kick-off meeting play in project communication management?
It sets a shared starting point. The kick-off meeting should communicate the project purpose, objectives, scope, key milestones, roles and how the team will communicate, so everyone starts with the same understanding.