Day 17: Build a Project Communication Plan

The Concept

Communication is part of project design. Without a clear rhythm, information arrives late, decisions are repeated, and people create their own versions of the truth. Too much communication creates a different problem: important signals disappear in volume.

Purpose before channel

Start with the purpose: inform, decide, coordinate, escalate, learn, or reassure. Then choose the channel. A status update may be asynchronous. A conflict or decision with competing interests may need a conversation. The channel should serve the purpose, not simply repeat the team's habits.

Make ownership visible

Every recurring communication needs an owner and a source of truth. If the project manager is the only person who can explain progress, the project is fragile. Use AI to draft formats and reminders, but distribute ownership where the information originates.

Example: design for different information needs

Consider a system implementation with a delivery team, sponsor, operations group, and affected users. The delivery team needs a short weekly coordination session for blockers and decisions. The sponsor needs a fortnightly outcome and risk update with explicit asks. Operations needs readiness information tied to training and support. Users need a clear message when the change affects their work.

Sending the same long status email to all four groups would create noise and still leave gaps. A communication plan gives each group a purpose, owner, trigger, and source. It also makes the gaps visible: perhaps nobody owns the user-facing readiness message, or decisions are being made in chat without entering the decision log.

Design the escalation route

Communication is not complete until people know what to do when a message signals a problem. Define when an issue stays with the team, when it goes to the sponsor, and what information an escalation must include. A route can be simple: situation, impact, options, recommendation, decision needed, and required-by date.

Keep asynchronous work honest

Asynchronous communication works when the reader can understand the context, respond in the right place, and know when a response is needed. Do not label a message asynchronous if the real expectation is an immediate discussion. A short meeting may be kinder when the issue is sensitive, ambiguous, or likely to produce competing interpretations.

Review the plan as the project changes

Communication needs change at discovery, build, testing, launch, and transition. Review the plan when stakeholders change, risk increases, or a new decision forum appears. Retire messages that no longer serve a purpose so the plan stays usable.

A final check before sharing

For each audience, ask: what do they need to know, what can they do with it, and where will they find the latest version? If the answer is unclear, the communication plan is not finished. Fewer, clearer messages are usually stronger than a full calendar of updates.

Give every message a contract

A useful communication entry states the audience, purpose, owner, trigger, channel, and expected response. The trigger might be a weekly cadence, a milestone, a decision, a risk threshold, or a change in customer impact. Avoid vague entries such as “keep leadership informed.” Define what leadership should receive and what action may follow.

Protect the source of truth

Chats and email are useful for movement, but they are poor long-term records when decisions and actions remain buried inside them. Link the message to the decision log, action tracker, plan, or approved brief. If the source changes, update the link or reference rather than leaving several conflicting copies in circulation.

Measure whether communication works

Look for signs of communication failure: repeated questions, decisions made without the right people, late discovery of changes, or stakeholders using different dates. These signals are not a reason to send more messages automatically. They are a prompt to improve the message, audience, timing, or source of truth.

Review the plan at each major phase. The right rhythm during discovery may be excessive during build, while launch may require more frequent operational communication. Adapt deliberately and tell people what changed.

Communication is successful when people can act with less confusion, not when every channel is busy.

Ask one recipient whether the plan helped them make a decision or act earlier. That answer is more useful than counting how many updates were sent.

Use this today

An owner should be able to update the plan without asking the project manager to interpret every message.

That keeps communication ownership close to the work.

It also reduces avoidable bottlenecks.

Small ownership improvements compound over time.

The plan should make that ownership visible.

Use the finding to adjust the plan at the next review.

Remove messages that no longer help anyone understand, decide, or act.

This keeps the plan light enough to maintain when the project becomes busy.

List every recurring project meeting and update. For each, write its purpose and decision or output. Retire anything with no clear value, then add the missing communication that would help a stakeholder act earlier.

Remember this

• Communication should help someone understand, decide, or act.
• A meeting is not a source of truth.
• The best communication plan reduces noise and increases visibility.