3.5Communication, meetings & reporting
The essentials in 30 seconds
- A project manager does a linking job: good communication prevents most relationship problems.
- A communication plan anticipates who to inform, about what, how often and through which channel.
- Framed meetings (objective, agenda, decision log) + tailored reporting (synthetic committee, detailed team).
Running case — Bilal aligns everyone on one page
Final act: Bilal sees the steering committee disconnecting (too much detail), the team complaining (contradictory information) and the client worrying (radio silence). He sets a simple plan: a 30-minute weekly team point with a decision log, a one-page monthly committee report (health, alerts, expected decisions), a client message at each milestone. When a delay threatens, he announces it early with 2 options: trust rises back.
Final episode of cases 3.1-3.4 — Bilal circulates the right information.
1. A linking job
A project manager spends much of the time communicating. A communication plan anticipates who needs which information, how often and in which form — from the monthly committee to the weekly team point. Bilal lists his audiences (committee, team, client) and sets info, frequency and channel for each.
Good communication prevents most relationship problems: most tensions come from missing, late or ill-adapted information.
2. Meetings, reporting, audience
This goes through effective meetings (objective, agenda, decision log with who / what / when) and clear reporting: a synthetic, honest, decision-oriented account. Bilal circulates each log fast, before memories diverge.
The right reflex: tailor the message to each audience — the committee wants essentials and arbitrations, the team wants operational detail. And bad news is announced early, factually, with 1-2 solutions: alerting in time builds trust, hiding destroys it.
The meeting that could have been a message
A meeting with no objective and no log is a project moving backwards while meeting.
🔎 Concrete example — Announcing bad news
Early, factual, with options.
Do not hide a problem hoping to catch up (it grows).
Present: facts + impact + 1-2 solutions / arbitrations.
→ alerting in time builds trust; hiding destroys it.Outcome: aligned, confident stakeholders.
Reflex: always a decision log after a meeting.
Section vocabulary
- Communication plan
- Who to inform, about what, how often and through which channel, throughout the project.
Simple example: Bilal's plan: weekly team, monthly committee, client at each milestone.
What it is not: information as you go, with no regularity.
Reflex: write the plan and stick to it no matter what.
- Reporting
- Regular communication of progress and project health, synthetic and decision-oriented.
Simple example: Bilal's monthly page: health, alerts, expected decisions.
What it is not: a rare exhaustive brick nobody reads.
Reflex: regular, honest, one page, decision-oriented.
- Project meeting
- A framed exchange time (kick-off, tracking, committee) with an objective and a decision log.
Simple example: Bilal's 30-minute weekly point, agenda held.
What it is not: a discussion with no objective and no recorded follow-up.
Reflex: no written objective = no meeting.
- Minutes (record)
- A meeting summary: decisions, actions (who / what / when), pending points; to circulate fast.
Simple example: Bilal sends the log the same day before memories diverge.
What it is not: a 10-page record three weeks later.
Reflex: circulate fast, short, with named actions.
- Audience tailoring
- Adjusting detail level and angle to the audience served.
Simple example: Synthetic committee, detailed operational team.
What it is not: the same technical brick for all audiences.
Reflex: before each message: "for whom, to decide what?".
In practice — Building your communication setup
- Set a communication plan: audiences (committee, team, client), and for each the info, frequency, channel.
- Frame your key meetings (kick-off, weekly tracking, committee): objective, agenda, and always a decision log.
- Design a synthetic reporting template (one page): progress, alerts / risks, expected decisions.
- Tailor each message: the committee wants essentials and arbitrations; the team wants operational detail.
Ready-to-say script — announcing a delay to the committee (1 min)
"We will be 10 days late on delivery: testing has been stalling for two weeks. Impact: risk on go-live. Two options: targeted reinforcement to hold the date, or a minor scope arbitration. I recommend the first, and I await your arbitration."
To say early, facts + impact + 2 options + recommendation: the alert becomes a decision.
Copy-paste template — communication plan + express log
COMMUNICATION PLAN — AUDIENCE: _______________ | INFO: _______________
FREQUENCY: _______________ | CHANNEL: _______________
LOG OF: _______________ | DECISIONS: _______________
ACTIONS (who / what / when): _______________
PENDING POINTS: _______________ | CIRCULATED ON: _______________Very small business / tight budget
A 5-line weekly message (done, left, blocker, need) beats a big monthly report.
SME in Algeria
Bilal backs writing with a brief call for sensitive decisions: speech unblocks, writing traces.
Remote team
A systematic log after each video call: named decisions and actions, otherwise the call evaporates.
Worried client
A short message at each milestone (done, impact, next): radio silence breeds worry.
✓ Best practices
- Anticipate who to inform, about what, how often (communication plan).
- Frame each meeting (objective, agenda, decision log).
- Announce bad news early, with options.
✗ Common pitfalls
- Communicating as you go, with no plan and no regularity.
- Meetings with no objective and no decision log.
- Hiding a problem hoping to catch up (it grows).
Key takeaways
- The project manager does a communication and linking job.
- A communication plan anticipates who to inform, about what, when, how.
- Framed meetings (objective, agenda, decision log) + clear reporting.
- Tailor the message to the audience (synthetic committee, operational team).
48h challenge — apply tomorrow
Send your next one-page report (health, alerts, expected decisions) to the right audience, with a decision log of your last meeting.
- I can cite the 3 pillars (plan, meetings, reporting).
- I tailor the message to the audience.
- I sent 1 report + 1 log.
Frequently asked questions
How often should reporting be done?
It depends on audience and stakes: a weekly team point, a monthly committee report for instance. Rule: frequent enough to decide and react, without drowning. Regular, honest reporting, even when all is not well, builds trust; late bad surprises destroy it. Better reliable, expected information than a sporadic grand report.
How to announce bad news (delay, overrun)?
Early, factually, with options. Do not hide a problem hoping to catch up: it grows. Present facts, impact, and 1-2 solutions or arbitrations. A project manager who alerts in time with proposals builds trust; one who hides until explosion loses it. Arriving with the problem AND leads turns the alert into a constructive decision.
A delay threatens Bilal's project. Which announcement protects trust?