Write a Communication Plan People Actually Read
Ask ten project managers if they have a communication plan and nine will say yes. Ask to see it being used and the room goes quiet. The document exists — usually a tidy table buried in a project folder — but the team works off email threads, hallway chats, and whatever the last meeting decided. With distributed and hybrid teams now the norm, those informal channels leak. A communication plan that people follow is not a deliverable you write once; it is a working agreement you keep light enough to live by.
The reason most plans fail is that they answer the wrong question. They describe what the project manager will produce — a status report, a steering deck — rather than what each stakeholder actually needs to make their decisions. Flip that, and the plan starts pulling its weight.
Start with the audiences, not the artifacts
Before you decide on any report or cadence, list who has a stake in the project and what each of them needs from it. A sponsor needs to know if you are on track and where you need a decision. A delivery team needs clarity on priorities and blockers. An affected business unit needs enough warning to prepare. The same update rarely serves all three.
List the stakeholders. Name real people and groups, not abstract roles. "The sponsor" should have a name beside it.
Name what each one needs. Decisions, early warning, reassurance, detail — be specific about the job the communication does for them.
Choose the channel to fit. Match each need to a channel and rhythm: a five-line weekly email, a fortnightly review, a live dashboard, a quick async video.
Assign an owner. Every line in the plan needs a named person responsible for sending it. A channel with no owner is a channel that goes silent.
Set the trigger, not just the calendar. Some communications are scheduled; others fire on an event, like a slipped milestone or a budget threshold being crossed.
Keep it small enough to survive
A communication plan that lists fifteen reports will produce two and disappoint everyone. The discipline is subtraction. For most projects, three or four channels carry almost all the value:
A short, predictable status update — same day, same format, every week — so people stop asking "how's it going?"
A decision log that records what was decided, by whom, and when, so distributed teams stop relitigating settled questions.
An escalation path everyone knows in advance, so bad news travels fast instead of being held until the next meeting.
A single source of truth — one place where the current plan, risks, and status actually live, not five competing copies.
For hybrid teams, write down which conversations happen live and which happen in writing. The default should lean toward written and asynchronous, because a decision captured in text survives time zones and reaches the person who was out that day. Reserve live meetings for the work that genuinely needs discussion.
Make following it the easy path
The real test of a communication plan is whether following it is easier than ignoring it. If your weekly update takes an hour to assemble, you will skip it under pressure. If the status lives in a tool nobody opens, people will email you instead. Build the plan around habits your team already has, lower the effort of each touchpoint, and review the plan itself once a month — drop what no one reads, strengthen what people rely on. A plan that is honest about how the team actually communicates beats a perfect one that nobody opens.
If you want communication on your project to be a strength rather than a guessing game, XNM's program & project delivery advisory can help you set up cadences and channels your team will keep using.