Managing Project Communications

Why This Matters: Communication Failure Is the #1 Project Killer

PMI's Pulse of the Profession surveys consistently reveal the same finding: poor communication is the primary contributor to project failure. Not budget overruns. Not scope creep. Not technical complexity. Communication.

And the reason is deceptively simple: every other project management process depends on information flowing to the right people, at the right time, in the right format. When that flow breaks down, decisions are made on stale data, stakeholders lose confidence, risks go unreported, and teams work at cross-purposes.

Managing project communications during execution is not about sending more emails or scheduling more meetings. It is about designing and controlling the information architecture that keeps the entire project organism alive.

Core Principle: The performance reporting process involves the distribution of performance information to key stakeholders, specifically capturing how resources are being used to achieve project objectives.

---

What Is "Manage Communications"?

Manage Communications is the PMBOK process responsible for creating, collecting, distributing, storing, and dispositioning project information in accordance with the Communications Management Plan. During execution, this process ensures that stakeholders receive the information they need to make informed decisions and maintain confidence in the project.

The PMBOK Process View

Communications — Management Plan

Work Performance — Reports

Enterprise Environmental — Factors

Organisational — Process Assets

Manage — Communications

Project — Communications

PM Plan Updates

Project Document — Updates

OPA Updates

Relationship details

From	Relationship	To
Communications — Management Plan	leads to	Manage — Communications
Work Performance — Reports	leads to	Manage — Communications
Enterprise Environmental — Factors	leads to	Manage — Communications
Organisational — Process Assets	leads to	Manage — Communications
Manage — Communications	leads to	Project — Communications
Manage — Communications	leads to	PM Plan Updates
Manage — Communications	leads to	Project Document — Updates
Manage — Communications	leads to	OPA Updates

---

How It Works: The Dimensions of Communication

Communication Forms

Project communication is not monolithic. It operates across multiple dimensions simultaneously, and the PM must consciously choose the right form for each situation:

Internal" --> "External · Informal" --> "Formal

Governance Reviews & Audits

• Classify relevant stakeholders here

Stakeholder Reports & Briefs

• Classify relevant stakeholders here

Team Stand-ups & Chat

• Classify relevant stakeholders here

Contractor Coordination

• Classify relevant stakeholders here

Quality Communication

Not all communication is equal. The course materials identify five hallmarks of quality communication:

1. Expressing oneself simply and objectively — Clarity over cleverness
2. Effective listening — Understanding before responding
3. Contributing information effectively and with tact — Delivering hard truths without destroying relationships
4. Acknowledging and using the expertise and advice of others — Leveraging collective intelligence
5. Explaining what you and your team are doing — Transparency builds trust

The Communication Formula: Quality communication = Clarity + Listening + Tact + Humility + Transparency. Remove any one element and trust begins to erode.

---

Performance Reporting: The Backbone of Project Control

Performance reporting is a control mechanism that produces standardised reports and reviews at defined intervals. It transforms raw work performance data into actionable intelligence for decision-makers.

Reporting Frequency

The Communications Management Plan defines when reports are due. Common triggers include:

---

Report Types

The course materials define four distinct report types, each serving a different purpose in the project information architecture:

Standard Project — Report

Milestone — Report

Quarterly — Report

Project/Phase — Completion Report

Exception — Report

Stakeholders

Program — Management

All Stakeholders — (Wide Distribution)

Escalation — Path

Relationship details

From	Relationship	To
Standard Project — Report	Routine status	Stakeholders
Milestone — Report	On achievement	Stakeholders
Quarterly — Report	Periodic summary	Program — Management
Project/Phase — Completion Report	Phase/Project close	All Stakeholders — (Wide Distribution)
Exception — Report	Significant deviations	Escalation — Path

Standard Project Report Format

Milestone Report Format

Quarterly Report Format

Project/Phase Completion Report Format

---

Exception Reporting

Exception reports are triggered by significant deviations from the project plan. They sit outside the regular reporting cycle and demand immediate attention. Triggers include:

• Failure to achieve a milestone
• Significant variations from plan, schedule, or budget
• Significant trends in under- or over-achievement of expenditure
• Unforeseen changes in project team requirements or unresolved conflict
• Significant changes in risk assessment

The Exception Reporting Rule: If a deviation is large enough that a stakeholder would be surprised to learn about it at the next scheduled report, it requires an exception report now. Surprise is the enemy of stakeholder trust.

---

Stakeholder Relationship Management

The supplementary readings reinforce a critical truth: communication is not just about transmitting information — it is about managing relationships. Michael Wood's four principles of stakeholder relationship management provide the strategic lens:

Principle 1: Consider the Organisation Culture and Political Environment Every organisation has its own values, beliefs, and behaviours. Subcultures exist within the macro-culture. The PM must adapt communication style to fit each stakeholder group's expectations, agendas, and risk appetite.

Principle 2: Fit the Communication Plan to the Project's Impact All projects need communication plans, but the scale and formality should match the project's impact on the organisation. A minor internal tool upgrade does not need the same communication infrastructure as a multi-year defence procurement program.

The Trust Factor: Joe Wynne's article on trust and stakeholders illustrates that communication failures compound. When team leads appear unprepared in stakeholder meetings, or when deliverables are submitted without quality review, stakeholders lose confidence — and once lost, trust takes far longer to rebuild than it took to destroy.

---

Control Communications

Throughout the project lifecycle, communications must be monitored and controlled to ensure stakeholder information needs are met. This process focuses on optimising information flow — ensuring neither too much nor too little information reaches each audience.

Information Management Systems

In the project context, information management systems provide an efficient means to capture, store, and distribute information. Distribution formats include:

• Table reporting
• Spreadsheet analysis
• Presentations
• Letters
• Emails

Visual Reporting Advantage: Andrew Makar's article on visual reporting makes a compelling case: people skim reports rather than read them. Visual formats — dashboards, one-page summaries, traffic-light indicators — make it easier for stakeholders to absorb status and engage in meaningful conversation about scope, resource, and timeline concerns.

Work Performance — Data

Performance — Reporting

Project — Communications

Stakeholder — Feedback

Change — Requests

PM Plan — Update

Relationship details

From	Relationship	To
Work Performance — Data	leads to	Performance — Reporting
Performance — Reporting	leads to	Project — Communications
Project — Communications	leads to	Stakeholder — Feedback
Stakeholder — Feedback	leads to	Change — Requests
Change — Requests	leads to	PM Plan — Update
PM Plan — Update	leads to	Work Performance — Data

---

The Communication Channels Formula

As a team grows, the number of potential communication channels increases exponentially. The formula for calculating communication channels is:

$$C = \frac{n(n-1)}{2}$$

Where C = number of communication channels and n = number of stakeholders.

The Scaling Problem: A project with 10 stakeholders has 45 potential communication channels. At 50 stakeholders, that number explodes to 1,225. This is why the Communications Management Plan is not optional — without it, information flows chaotically and critical messages get lost in noise.

---

The Pitfalls: Where Communications Management Goes Wrong

1. Reporting Without Purpose Producing reports because the schedule says to, not because they contain actionable information. Every report should answer: What decision does this enable?

2. Over-Communication Flooding stakeholders with information they do not need. This creates noise, causes important messages to be missed, and erodes confidence in the PM's judgement.

3. Under-Communication on Bad News The instinct to delay or soften bad news is natural — and destructive. Exception reports exist precisely for this. Stakeholders can handle bad news; they cannot handle surprises.

4. Ignoring the Invisible Customer Brad Egeland's article warns about the scenario where the customer disengages from the project. Even if the customer stops attending meetings, the PM must still deliver to their requirements. Proactive communication — even when it is one-directional — protects the project.

5. One Communication Style for All Stakeholders Senior executives need one-page dashboards. Technical leads need detailed technical reports. Contractors need contractual performance data. Tailoring communication to the audience is not a luxury — it is a requirement.

---

Real-World Application: The Defence & Heavy Engineering Context

In defence and heavy engineering projects, communications management takes on additional complexity:

• Classification and security clearances restrict who can receive what information
• Configuration management requires formal documentation of every design change
• Multi-tiered contractor structures demand reporting hierarchies (prime contractor → sub-contractor → sub-sub-contractor)
• Government audit requirements mandate specific report formats and retention periods
• Geographic distribution (international supply chains, remote sites) requires deliberate use of communications technology to bridge distances

The PM in this environment must design a communication architecture that satisfies governance requirements while still keeping information flowing fast enough for effective decision-making.

Project Team — • Daily stand‑ups — • Informal updates

Program Management — • Monthly reports — • Formal reviews

Steering Committee / Sponsors — • Quarterly briefs — • Executive dashboard

External Stakeholders / Regulators — • Milestone reports — • Exception reporting

Relationship details

From	Relationship	To
Project Team — • Daily stand‑ups — • Informal updates	leads to	Program Management — • Monthly reports — • Formal reviews
Program Management — • Monthly reports — • Formal reviews	leads to	Steering Committee / Sponsors — • Quarterly briefs — • Executive dashboard
Steering Committee / Sponsors — • Quarterly briefs — • Executive dashboard	leads to	External Stakeholders / Regulators — • Milestone reports — • Exception reporting
Program Management — • Monthly reports — • Formal reviews	leads to	Project Team — • Daily stand‑ups — • Informal updates
Steering Committee / Sponsors — • Quarterly briefs — • Executive dashboard	leads to	Program Management — • Monthly reports — • Formal reviews
External Stakeholders / Regulators — • Milestone reports — • Exception reporting	leads to	Steering Committee / Sponsors — • Quarterly briefs — • Executive dashboard

---

Key Takeaways

• Manage Communications is the process that ensures the right information reaches the right stakeholders at the right time during execution.
• Communication operates across four dimensions: medium (written/oral), direction (internal/external), formality (formal/informal), and hierarchy (vertical/horizontal).
• Performance reporting is a control mechanism with four standard formats: Standard, Milestone, Quarterly, and Project/Phase Completion — plus Exception Reports for significant deviations.
• Control Communications optimises information flow and prevents both over- and under-communication.
• The communication channels formula $$C = \frac{n(n-1)}{2}$$ explains why communications management becomes exponentially more complex as stakeholder numbers grow.
• Visual reporting is more effective than text-heavy reports because stakeholders skim, not read.
• Stakeholder trust is built through consistent, tailored, transparent communication — and destroyed by surprises and poor preparation.

---

References:
PMBOK Guide, 5th Edition, PMI, 2013 — Chapter 10: Project Communications Management
Wood, M.R. (2009). Stakeholder Relationship Management: A Primer. ProjectManagement.com
Makar, A. (2011). Improving Project Status with Visual Reporting. ProjectManagement.com
Wynne, J. (2009). Trust, Business Stakeholders and Your Workforce. ProjectManagement.com
Egeland, B. (2011). Attack of the Invisible Customers! ProjectManagement.com