Communication Management in PM²: the right information for the people who must act
Twenty-first article in the “Learning PM² Through a Project” series
A project does not improve because it generates more messages, meetings and slides. It improves when people receive reliable, understandable and timely information, sufficient to decide or act.
In PM², Communication Management plans, produces, distributes and manages project information. It is the nervous system of governance: without adequate communication, decisions, risks, issues and changes arrive late or remain ambiguous.
Communication does not mean indiscriminate distribution
Every communication should answer five questions:
| Question | Example |
|---|---|
| Why? | Inform, request a decision, gather feedback, coordinate action. |
| To whom? | PO, technical team, pilot users, PSC, supplier, all stakeholders. |
| What? | Status, risk, issue, decision request, change, operational instruction. |
| When? | Daily, weekly, at a milestone, when a trigger occurs. |
| How? | Dashboard, report, meeting, ticket, email, demo, guide, collaboration channel. |
Sending the same long report to everyone is often the opposite of transparency: it hides what each person actually needs to understand or do.
Communication Management and Stakeholder Management
The two topics are connected but not identical.
| Stakeholder Management | Communication Management |
|---|---|
| Analyses influence, interests, impact and required engagement level. | Organises information flows, content, channels, frequencies, formats and communication responsibilities. |
| Answers: “who should be engaged, and for what objective?” | Answers: “which information should flow, how and when?” |
The Stakeholder Matrix guides the Communication Management Plan. If a stakeholder needs to make a decision, adding them to a mailing list is not enough: communication must present the choice, impact, deadline and required authority.
The Communication Management Plan
The plan can be lightweight, but should make the minimum explicit:
| Element | What to define |
|---|---|
| Audience | Recipients and their information need. |
| Information | Content, detail level and expected action. |
| Owner | Who prepares, checks and sends or presents. |
| Frequency / trigger | Cadence or event that activates the communication. |
| Channel and format | Report, meeting, dashboard, ticket, demo, email, repository. |
| Confidentiality and retention | Who can access it and where the official version remains. |
An effective plan also distinguishes push communications (actively sent, such as an urgent alert) from pull communications (available for consultation, such as an updated dashboard).
Project reporting: status, not narrative
A useful status report need not tell the story of every activity completed. It should make deviations, forecasts, risks, issues, required decisions and upcoming milestones clear.
| Section | Question it answers |
|---|---|
| Overall status | Is the project within agreed limits? |
| Progress and milestones | What is complete and what happens next? |
| Deviations and forecasts | What differs from plan and what impact is expected? |
| Main risks and issues | What could threaten, or is threatening, the project? |
| Decisions / support required | Who must decide what, by when? |
| Actions and owners | What happens now and who handles it? |
A traffic light without explanation or action is of little use. “Red” should say compared with which baseline, for what reason, with what impact, and which action or decision is proposed.
Meetings: a means, not an outcome
A meeting is justified when it creates alignment, resolves a blockage, enables a decision or produces a clear output. Before convening one, clarify:
- objective and expected decision or output;
- necessary participants, not merely available participants;
- preparatory material and starting data;
- facilitation, timebox and closing actions;
- where decisions and follow-up will be recorded.
Minutes should be proportionate. For an operational meeting, decisions, actions, owners and dates may be enough. A governance decision may need a more formal record.
The Annotatio case: one communication for each need
In the Smart Bookings project, not everyone needs the same information.
| Recipient | Information | Frequency / trigger | Channel | Expected action |
|---|---|---|---|---|
| PO/BM | Status, benefits, risks and priority decisions. | Weekly; immediately if tolerances are exceeded. | Concise report + decision meeting. | Decide business trade-offs. |
| Annotatio team | Activities, dependencies, issues and quality criteria. | Daily / continuous. | Board, stand-up, tickets. | Coordinate and remove blockages. |
| Pilot gym managers | Test plan, changes, instructions and feedback collection. | Before trials and at each release. | Demo, short guide, support channel. | Test and validate. |
| Floor collaborators | New flow, activation date and available support. | Before go-live and during first week. | Short training + operating instructions. | Adopt the process. |
| PSC | Decisions outside tolerance, concise status and options. | At gates / escalation. | Decision paper and meeting. | Decide or ratify. |
Communication can be technically correct and still ineffective: telling collaborators “the release is in production” does not explain what they need to do differently the next day.
Communicating bad news
Delaying bad news in order to “first have a solution” is often a mistake. For material information, communicate early what is known and clearly distinguish:
- verified facts: what happened or what was measured;
- assessment: estimated impact and confidence level;
- actions in progress: owner, next evidence and date;
- decision required, if needed.
This avoids both alarmism and false optimism.
Information distribution and version control
Documents, plans, logs and decisions need a trusted source. When many uncontrolled copies circulate, a project can spend days discussing an outdated version.
Define where official artefacts reside, who may change them, how versions are approved and which information is confidential. This is not an administrative detail: it is a condition for fact-based decisions.
Do not confuse these
| Statement | Correction |
|---|---|
| “More communication means more transparency.” | Transparency requires relevant, accessible and actionable information. |
| “The status report is to justify the PM’s work.” | It enables governance to understand status, deviations, risks and required decisions. |
| “A meeting is a decision.” | A decision must be explicit, recorded and accompanied by actions. |
| “A dashboard removes the need to communicate.” | A dashboard informs; it does not replace discussion, decisions or engagement. |
Three questions to anchor it
- Who needs this information, and which action should they be able to take?
- Which channel and level of detail are proportionate to urgency and impact?
- Where is the official version of this decision or document?
Flashcards
Q: What is the Communication Management Plan for?
A: To define audiences, contents, owners, frequencies, triggers, channels, formats and information-management rules.
Q: What should a useful status report contain?
A: Status against baselines, progress, forecasts, deviations, risks, issues, required decisions and next actions.
Q: Why is version control important?
A: It ensures stakeholders and teams decide and work using the same reliable information.
Exam-style question
The PM sends every stakeholder a ten-page weekly report. An urgent release-date decision is on page eight and nobody responds by the deadline.
What is the correct approach?
Answer: an urgent decision needs targeted communication to the competent decision-maker, with concise context, options, impact, recommendation and decision deadline. The general report may remain the detailed source, but does not replace the decision request.
Source
Communication Management, the Communications Management Plan, project reporting and information distribution are covered in the European Commission’s PM² Methodology Guide 3.1.
Next: Managing schedule, cost and resources, for turning planning and monitoring into concrete forecasts and decisions.