Delivering and monitoring communications

A good plan is wasted if the reports nobody reads, the meetings drift and the dashboard is always green until the week before disaster. This lesson covers the delivery side of the plan and manage communication task: writing status reports that drive decisions, designing dashboards, running meetings that produce outcomes, communicating earned value results to non-specialists, using virtual and AI tools responsibly, and monitoring whether communication is actually working.

Status reports that drive decisions

A status report exists to help readers decide and act. Most poor reports fail in one of three ways: they describe activity rather than progress against the plan, they bury the important message under detail, or they hide bad news. A strong report starts with a short summary that says whether the project is on track, what has changed and what decisions are needed from the reader, then supports it with evidence.

Status colours and the watermelon problem

Red, amber and green (RAG) ratings are widely used because they are quick to read. They work only if everyone uses the same definitions. A typical set: green means on track within agreed tolerances; amber means at risk of breaching tolerance, with a recovery plan in hand that the project can deliver itself; red means tolerance is breached or will be without help, and a decision is needed from above. Without definitions, people report green until they are certain of failure, producing so-called watermelon projects: green on the outside, red inside.

Project managers prevent watermelon reporting by defining RAG criteria in the communications plan, tying ratings to measurable thresholds where possible (for example, schedule variance beyond 5 per cent turns amber), rewarding early warnings rather than punishing them and visibly acting on amber ratings. A sponsor who reacts to an amber rating with blame will receive green ratings until the project fails.

Dashboards

A dashboard is a visual summary of status, usually published for pull communication. Good dashboards show a small number of measures that matter to their audience, compare actual results with targets or baselines, show trends rather than single points, and make exceptions stand out. They avoid decoration, three-dimensional charts and colour-only signals. An executive dashboard might show milestone status, cost and schedule performance indices, top risks and benefits forecasts; a team dashboard might show burndown, cycle time and defect trends.

Communicating earned value to non-specialists

Earned value management (covered in depth in CON-310 and in the Process courses of this series) produces precise indices, but stakeholders rarely want indices; they want to know whether the project will finish on time and on budget and what to do about it. The project manager's job is to translate.

Meetings that produce outcomes

Meetings are the main interactive channel and the most expensive one. A productive meeting has a stated purpose, an agenda sent in advance, the right attendees, a facilitator who keeps time and draws out quieter people, and documented outcomes: decisions, actions with owners and dates, and open questions. Minutes need not be long; a short note of decisions and actions, sent within a day, is usually more useful than a transcript.

Virtual tools and AI assistants

Distributed and hybrid projects rely on collaboration platforms, chat, shared documents and video. These tools make communication faster but also noisier: important decisions disappear into chat threads, and people in different time zones miss context. Good practice includes agreeing which channel is used for what (for example, chat for quick questions, the issue tracker for issues, a decision log for decisions), summarizing decisions in a durable place and respecting working hours.

Many organizations now use AI tools to transcribe and summarize meetings, draft reports and translate documents. They can save time, but the project manager remains responsible for accuracy and confidentiality. Summaries can miss nuance or misattribute statements, translations can change meaning, and uploading confidential information to an unapproved tool can breach contracts or privacy law. Use only tools your organization has approved, tell participants when meetings are recorded or transcribed, review AI-generated content before sending it, and never let a summary replace a decision record that the decision makers have confirmed.

In Canada, recording or transcribing a meeting collects personal information, so notice and purpose limits under PIPEDA or provincial privacy law apply, and federal and provincial privacy commissioners have issued guidance on generative AI. Quebec's privacy law also requires organizations to inform people when decisions about them are made exclusively by automated processing.

Monitoring communication effectiveness

Monitoring asks whether communication is reaching the right people and producing the intended understanding and action. Useful indicators include whether decisions are made on time, whether stakeholders are surprised at reviews, the number of repeated questions on the same topic, attendance and participation in key meetings, use of the dashboard or repository, and direct feedback from short surveys or conversations. When monitoring shows a problem, the response might be a change of channel, frequency, format or messenger, recorded as an update to the communications management plan.

Communicating in a crisis

Sometimes a project faces a crisis: a serious safety incident, a data breach, a failed launch that affects customers, or intense media attention. Crisis communication follows the plan's event-triggered rules but needs extra discipline. Establish a single source of truth and one authorized spokesperson; tell affected people and regulators quickly and accurately what is known, what is not yet known and when the next update will come; avoid speculation; coordinate legal, communications and executive review without letting it delay essential safety information; and keep a log of what was communicated, to whom and when. After the crisis, review what worked and update the plan.