Skip to content

Chapter 3 of 6

Communication Practices

Communication is the visible engine of stakeholder management and benefits from being designed rather than improvised. A communication cadence is the planned rhythm for updates, decisions, and check-ins, while a stakeholder communication plan specifies what is communicated, to whom, by whom, through which channel, on what cadence, and with what success criteria. Regular updates build trust and reduce the anxiety that appears when people feel uninformed. A strong update is concise, honest about risk, clear on decisions, and explicit about what is needed next; the BLUF ("Bottom Line Up Front") style leads with the headline, decision, or ask and then layers on supporting context. The right length for a status update is long enough to cover progress, risk, and asks but short enough to be read in under five minutes by the intended audience.

Different audiences need different shapes of communication, which is where stakeholder tailoring comes in: adjusting message depth, timing, and framing based on each audience's needs. The rule of three helps working memory — leading with at most three points, three risks, or three asks in a single briefing. A one-pager summarizes goal, status, risks, and decisions on a single page intended to be read in under two minutes, and a briefing pack bundles the one-pager with supporting data, a decision log, and a risk register as a pre-read for review meetings. Pre-reads are valuable because they give people time to process information before a meeting so the discussion itself can be higher quality. For audiences that want current data on stable metrics, a dashboard is often preferable to a written update because it supports self-service reading.

Two structural distinctions keep communication from degrading. Push communication is sent to the stakeholder (email, briefing) while pull communication is made available for the stakeholder to consult (dashboard, wiki, FAQ). Both are needed — push for relevance, pull for depth. Updates should always include explicit asks, because people respond faster when they know exactly what decision, input, or action is required from them. A stakeholder FAQ is a living document that captures the most common and most difficult questions with approved answers, reducing duplicated effort. Boards and working teams also need different shapes: a board update is a one-page summary of progress, risk, decisions, and asks, while a working update is detailed, task-level, and aimed at the executing team. The "no surprises" rule holds in executive communication — leaders expect to learn material issues from the project team first, not from peers, board members, or the press.

All chapters
  1. 1Foundations of Stakeholder Management
  2. 2Mapping and Prioritizing Stakeholders
  3. 3Communication Practices
  4. 4Stakeholder Dynamics and Hard Cases
  5. 5Negotiation and Alignment
  6. 6Decision Rights, Governance, and the Stakeholder Lifecycle

Drill it

Reading is not remembering. These come from the Stakeholder Management deck:

Q

What is stakeholder management?

Stakeholder management is the practice of understanding, aligning, and communicating with people who influence or are affected by a project or decision.

Q

Why does stakeholder management matter?

Strong stakeholder management reduces surprises, improves alignment, and makes execution smoother.

Q

Who counts as a stakeholder?

Anyone with influence over the work, dependency on the outcome, or exposure to its impact can be a stakeholder.

Q

What is a stakeholder map?

A stakeholder map is a simple view of who matters, what they care about, and how much influence they have.