12.3 Developing and Benefiting from a Project Communication Plan

12.3 Developing and Benefiting from a Project Communication Plan

APM BoK7 (3.3.1): "All projects, programmes and portfolios have communication plans that build from stakeholder analysis and outline the who, what, when, why and how of two-way communication between the team and the wider stakeholder environment. Effective communication plans include ways to receive feedback and measure effectiveness so that plans can be adjusted to have maximum impact."

That one passage answers both assessment criteria in this area. AC 9.4 (contents): who, what, when, why and how — plus feedback mechanisms and a way of measuring effectiveness. AC 9.5 (benefits to the project manager): because the plan builds from stakeholder analysis, it tells the project manager which stakeholders need which information, keeps communication genuinely two-way rather than broadcast, and lets the approach be adjusted when the feedback shows it is not landing.

Note the dependency APM builds in: a communication plan is developed from a stakeholder analysis. When a question asks which type of analysis a project manager needs in order to develop a proper communication plan, the answer is stakeholder analysis — not budget, resource or schedule analysis.

In project delivery, effective communication does not occur by accident. Without deliberate, upfront planning, project communications rapidly degenerate into reactive firefighting: senior executives receive overwhelming volumes of trivial operational trivia, technical teams are starved of strategic direction, and external stakeholders are blindsided by unexpected impacts.

The Project Communication Plan (often established as a core subsidiary plan of the overarching Project Management Plan) transitions the project from ad-hoc, chaotic information exchange into a structured, proactive, and predictable discipline.

---

The Derivation of the Communication Plan: Stakeholder Analysis

The Communication Plan does not originate in a vacuum; it is the direct operational output of stakeholder management and analysis (covered in APM BoK7 under stakeholder engagement).

During the concept and definition phases of the project lifecycle, the project manager identifies all individuals, groups, or organizations who can influence, are impacted by, or perceive themselves to be affected by the project. By evaluating stakeholders against a Power/Interest Matrix, the project manager categorizes audiences to determine their distinct communication profiles:

• High Power / High Interest (Key Players - e.g., Project Sponsor, Steering Committee): Require frequent, high-richness, personalized communication and active engagement.
• High Power / Low Interest (Keep Satisfied - e.g., Regulatory Bodies, Corporate Finance): Require formal, precise, compliance-oriented updates delivered through authoritative channels.
• Low Power / High Interest (Keep Informed - e.g., End-Users, Community Groups): Require regular, accessible, transparent communication to build goodwill and mitigate anxiety.
• Low Power / Low Interest (Monitor - e.g., General Public, Distant Suppliers): Require general broadcasting channels and passive information availability (e.g., website updates).

+-----------------------------------------------------------------------------------+
|              LINKING STAKEHOLDER ANALYSIS TO THE COMMUNICATION PLAN               |
+-----------------------------------------------------------------------------------+
|  Stakeholder Identification  --->  Power / Interest Matrix  --->  Information Needs|
|  (Who are the players?)           (Audience segmentation)       (What do they need?)|
|                                                                         |         |
|                                                                         v         |
|  Communication Plan Matrix  <---  Channel & Format Design  <---  Frequency & Senders|
|  (Living baseline document)      (Email, meeting, portal)       (Daily, weekly, PM)|
+-----------------------------------------------------------------------------------+

---

Core Contents of a Project Communication Plan

A comprehensive Project Communication Plan aligned with APM BoK7 must define the who, what, why, how, when, and by whom of every project communication flow. It typically contains the following core sections:

1. Stakeholder Identification & Audience Segmentation

Identifies the targeted individuals or groups. Stakeholders are categorized by organizational role, function, and relationship to the project (e.g., Project Sponsor, Steering Board, Core Development Team, Technical Quality Assurance, Commercial Vendors, Regulatory Authorities, and Business Change Champions).

2. Information Requirements & Content Definition

Defines the specific information needed by each audience group to fulfill their governance or operational role. The plan specifies whether the content consists of strategic milestone progress, budget burn rates, high-level exception reports, detailed technical defect logs, or user training timelines.

3. Communication Methods and Delivery Channels

Specifies the chosen vehicle for transmission, aligning channel richness with message intent. Channels include face-to-face steering group meetings, virtual video stand-ups, automated cloud dashboard links, formal signed contractual letters, or all-hands broadcast emails.

4. Frequency and Timing

Establishes the precise operational cadence for each communication event. The schedule defines whether updates occur daily (e.g., 15-minute morning stand-up), weekly (e.g., core team progress review), monthly (e.g., executive steering committee pack), or ad-hoc (e.g., immediate escalation upon breach of risk tolerance).

5. Sender / Communicator / Owner

Identifies the specific individual responsible for drafting, vetting, approving, and distributing the communication. Single-point accountability ensures messages are not delayed and prevents contradictory statements from emerging from different team members.

6. Formats and Standardized Templates

Establishes consistent visual and structural standards across the project. Templates include 1-page executive dashboard summaries, Red-Amber-Green (RAG) status tables, formal meeting minute templates, change request forms, and risk escalation briefs. Standardization reduces cognitive load for recipients and accelerates authoring.

7. Feedback, Verification, and Evaluation Mechanisms

Outlines how the project manager will verify that communications were received, decoded, and understood. This includes formal action logs, post-briefing Q&A sessions, stakeholder feedback surveys, and regular reviews of communication effectiveness during phase-end retrospectives.

8. Confidentiality, Security, and Distribution Constraints

Details data privacy rules, intellectual property protection protocols, commercial sensitivity classifications, and security clearances required for accessing proprietary project assets.

---

Sample Project Communication Plan Matrix

The core of the Communication Plan is typically documented as an actionable Communication Matrix. The table below illustrates a realistic matrix for an Enterprise Cloud Migration project.

---

Tangible Benefits of a Communication Plan

A robust, actively managed Communication Plan provides substantial strategic and operational benefits to the project manager, the delivery team, and overarching governance bodies:

1. Proactive Stakeholder Management and Expectation Control

A communication plan eliminates unpleasant surprises. Stakeholders know precisely when they will receive information and in what format. Proactive communication manages expectations around scope, cost, and timelines, preventing the frustration that occurs when stakeholders feel neglected or uninformed.

2. Elimination of Rumors, Gossip, and Project Politics

In the absence of authoritative project information, a vacuum is created. Human nature dictates that rumors, speculation, and negative gossip quickly fill information voids, creating anxiety and political resistance. A regular, reliable cadence of transparent communication maintains the project manager as the single source of truth.

3. Optimization of Time and Resource Utilization

Without a plan, communication is highly inefficient: senior leaders are overwhelmed with irrelevant low-level details (infobesity), while operational staff are starved of vital technical parameters. A communication plan ensures that every stakeholder receives only the information they require—no more, no less—conserving managerial time and cognitive energy.

4. Establishment of an Audit Trail and Governance Compliance

A structured plan ensures that stage-gate approvals, scope change authorizations, commercial agreements, and safety instructions are documented consistently. This provides an audit trail that protects the project manager and sponsoring organization during internal audits, external regulatory reviews, or legal disputes.

5. Enhanced Team Morale, Focus, and Cohesion

Project teams thrive when they understand the broader vision and know how their daily contributions contribute to project success. Regular, structured communication clarifies priorities, celebrates milestone successes, and ensures team members are not working at cross-purposes.

6. Accelerated Issue Escalation and Decision-Making

When unexpected issues or critical risk triggers occur, the communication plan provides pre-established escalation pathways. The project manager does not waste critical hours wondering whom to notify; the plan specifies exactly who has the delegated authority to authorize contingency reserves or alter project constraints.

---

Maintenance and Iterative Review of the Communication Plan

A critical tenet of the APM Body of Knowledge is that the Communication Plan is a living document. It is not created during the definition phase and filed away in an archive.

As the project progresses through its lifecycle:

• Stakeholders change: Key personnel resign, new executives join the board, or new suppliers are contracted.
• Stakeholder power and interest shift: A stakeholder with minimal interest during early design may acquire intense interest during live operational rollout.
• Project phases transition: The transition from development to operational testing demands an entirely different communication cadence and audience focus.

Best Practice: The project manager must review and re-baseline the Communication Plan at every stage gate, following major change requests, and during lessons-learned retrospectives to ensure information flows remain aligned with evolving project realities.