7.2.5: Formulating the Communications Management Plan

Formulating the Communications Management Plan 

Communication across an enterprise portfolio can't rely on informal check-ins, scattered email chains, or whatever message happens to reach someone first. A large capital portfolio running dozens of concurrent initiatives across different time zones and departments needs an explicit operating system for how information actually moves. That operating system is the Portfolio Communications Management Plan.

The Governance Foundation: Communication by Design, Not by Accident

The plan isn't an administrative checklist filed away once at kickoff and forgotten. It's an active, binding governance agreement dictating who receives a specific piece of portfolio information, why they need it, which channel it has to travel through, and on what predictable schedule it arrives. Without this kind of deliberate architecture, an organization ends up with real information asymmetry, where executive sponsors are making multi-million-dollar capital decisions based on stale assumptions, while delivery teams down below are still executing against a target that quietly stopped being accurate weeks earlier.

Architecture of the Enterprise Communications Matrix

The core artifact inside the plan is the communications matrix, which maps the stakeholder groups identified earlier in this chapter directly to a specific information payload, a governance purpose, a channel, and a delivery trigger. Table \(\PageIndex{1}\): A Sample Portfolio Communications Matrix lays out how different stakeholder tiers receive different payloads through different channels and cadences.

Table \(\PageIndex{1}\): A Sample Portfolio Communications Matrix  

Stakeholder Tier	Information Payload	Channel	Cadence
Executive Steering Committee	A two-page decision memo with portfolio health scorecards and risk distributions	Asynchronous board portal document	Monthly, five days before each gate review
Gatekeepers (Legal, Audit, Finance)	Statutory compliance audit trails and control logs	A formal, audited compliance sign-off system	Quarterly, mandatory before any public filing
Operational Business Unit Leaders and PMs	Real-time flow telemetry and cross-component dependency maps	An interactive information system dashboard	Continuous, with a biweekly sync forum
Front-Line Delivery Teams	Strategic context and delivered-capability demos	An all-hands briefing and a shared team wiki	Bimonthly, at sprint boundary milestones

Five fields make this matrix genuinely usable rather than decorative. Audience taxonomy sorts stakeholders by the power and salience discussed earlier in this chapter, so a high-power gatekeeper never gets buried in tactical noise while an operational owner still gets the granular detail they actually need. Payload specification bans vague entries like "status update" in favor of naming the exact artifact being sent, a specific sensitivity chart, a specific variance memo. Channel calibration matches the right platform to whether a message is transactional, collaborative, or needs to be auditable later. Trigger and cadence sets a predictable delivery rhythm or a clear event-based trigger, something like an automatic notice firing within 24 hours if a cost index drops below a set threshold. And accountable publisher names one specific person responsible for verifying and actually publishing the data, so responsibility never quietly diffuses across a group where nobody in particular feels on the hook.

Channel Strategy: Selecting and Calibrating the Medium

Not every communication platform serves the same purpose, and a major source of organizational failure is simply using the wrong one for a given message, a high-friction, real-time channel for static reference material, or a passive, asynchronous folder for something that actually needs urgent attention right now.

Collaborative and synchronous platforms, real-time messaging and video tools, exist for structured debate, live negotiation, and de-escalating a crisis in the moment. The failure to guard against here is making a genuinely binding decision inside an ephemeral chat thread and never transcribing that outcome into the formal decision log discussed in Chapter 5. A chat channel is a conversational medium, not an auditable record. Systems of record, document repositories and shared wikis, exist to archive signed charters, formal business cases, and immutable decision logs. The failure to guard against here is version proliferation, where uncontrolled local copies of the same strategic deck circulate and nobody's sure which one is actually current. Every link shared with a stakeholder should point back to one canonical file, not a personal copy. Active telemetry engines, the information systems and dashboards discussed in Chapter 5, exist for self-service analytics and continuous performance monitoring. The failure to guard against here is letting an ungoverned, rogue dashboard circulate that isn't actually pulling from the verified corporate data source underneath it.

Push vs. Pull Mechanics: Managing Cognitive Bandwidth

A key design choice in any communications plan is deciding what gets pushed directly to someone versus what simply gets made available for them to pull when they need it. Push communication lands directly in a stakeholder's inbox without any action on their part, and it needs to stay tightly curated, since over-pushing trains executives to create inbox filters that then cause them to miss the one urgent alert that actually mattered. Pull communication sits available in a central location, ready whenever someone wants to dig deeper, and it needs genuinely intuitive navigation. If an operational lead can't find a specific cross-component document within three clicks, the pull mechanism has already failed at its one job.

Establishing Predictable Governance Rhythms

Unscheduled, ad-hoc status requests place a real tax on delivery teams. Every time an executive sponsor demands an emergency update because of a market rumor, a program manager spends real time building slides instead of actually managing the work. A well-built communications plan replaces that unpredictability with a synchronized rhythm operating at three distinct speeds. Table \(\PageIndex{2}\): The Synchronized Portfolio Rhythm lays out three cadences, what happens at each one, and what it produces.

Table \(\PageIndex{2}\): The Synchronized Portfolio Rhythm  

Cadence	What Happens	Output
Weekly (Tactical)	Delivery flow sync and cross-component blocker triage	A blocker log
Monthly (Operational)	A portfolio health review, checking cost and schedule variance and stage-gate progress	A two-page executive memo
Quarterly (Strategic)	A strategic steering review covering capital tranche releases and roadmapping	A rebalanced portfolio

Publishing this calendar a full year in advance sets clear expectations on both sides. Executives know precisely when to expect verified performance data, which removes the temptation to demand an ad-hoc update every time something worrying crosses their desk. Project teams know exactly when their own numbers need to lock for reporting, which removes the last-minute scramble to reconcile a spreadsheet the night before a review.

Continuous Plan Auditing: Gap Analysis and Infrastructure Hygiene

The most dangerous assumption a portfolio manager can make is believing that sending an email or publishing a dashboard means communication actually happened. Real communication means the message was received and understood, not just transmitted. Keeping the plan honest requires a regular audit built around three checks.

Channel traffic analysis looks at whether people are actually engaging with what's sent to them, whether executives are opening a pre-read memo before a meeting or only during it, and whether a shared dashboard view is getting real traffic or sitting untouched. The information delta audit goes a level deeper, running short calibration interviews with a sample of stakeholders across every quadrant of the power and interest grid, asking something simple like what they believe the top strategic risks currently are. If their answer diverges sharply from what the information system actually shows, a real structural gap exists somewhere between the data and the person who's supposed to understand it, and the plan needs to change to close that specific gap. And pruning dead channels means formally retiring any recurring report that can't demonstrate a genuine, active audience within a set window, since portfolios tend to accumulate old spreadsheets and forgotten chat channels that quietly keep consuming attention long after anyone actually needed them.

Myth

A common myth treats the communications management plan as simply a spreadsheet of stakeholder names and email addresses, built once at kickoff and then filed away as finished. A static list like that isn't a communication plan. It's an administrative contact book. Communication needs shift constantly as executives turn over, strategies pivot, and organizations restructure, and a distribution list built at the start of a portfolio can be badly out of date within months. Blast-emailing an uncurated list also guarantees channel fatigue, since executives eventually build inbox filters to cope with the noise, and those same filters end up burying the one urgent risk notice that actually mattered. A real communications plan is a living operating agreement, governing information flow, channel choice, and verified comprehension continuously, not a document written once and never revisited.

That gap between sending a message and it actually landing is exactly what nearly derailed one real aerospace program.

When a Gap Reaches the Public

An avionics contractor once had an executive publicly announce a flight-testing date, unaware that engineering had already logged a four-month delay six weeks earlier. The delay existed only as a comment buried in a task tracker and a passing mention in an internal chat channel. It never reached the steering committee. The public contradiction damaged investor confidence and triggered a governance audit, not because anyone hid the information deliberately, but because no channel in the communications plan was actually designed to carry that kind of urgent signal upward.

Difficult Stakeholders and Communication Management

Every communications plan eventually runs into at least one stakeholder who doesn't fit neatly into a standard tier. Some read every message as an attack. Some respond to nothing until a deadline is already missed. Some dominate every forum they're part of, making it hard for anyone else's concern to get real airtime. A plan built only for cooperative, engaged stakeholders will quietly fail the moment one of these patterns shows up, so it's worth naming a few of them directly.

A chronically unresponsive stakeholder, one who never opens a memo or replies to a request, isn't necessarily disengaged. Sometimes the channel itself is wrong for them, and a five-minute phone call gets an answer that ten emails never will. A stakeholder who reacts defensively to any variance report, treating a yellow status as a personal accusation, usually needs the information framed around a shared problem to solve rather than a performance judgment to defend against. And a stakeholder who consistently escalates minor issues straight to the top, bypassing the agreed cadence entirely, is often signaling that they don't trust the normal channel to get them a fast enough answer, which is a gap in the plan worth fixing rather than a behavior to simply tolerate.

The instinct to treat a difficult stakeholder exactly like everyone else, sending the same memo on the same schedule regardless of how they actually respond to it, usually just repeats a pattern that already isn't working. Adjusting the channel, the framing, or the cadence for one specific person isn't favoritism. It's the same principle behind tailoring communication by power and interest, applied to behavior instead of formal authority. A communications plan that can't flex for the one stakeholder actually causing friction isn't really finished, no matter how well it works for everyone else on the list.