Stakeholder Communications Management
Plan the message, then the medium
Identify stakeholders, analyse their interest, influence, and information needs, then document the communication plan: who receives what, in which format, at what frequency, through which channel, and who owns it. Match format to audience. Executives usually need a milestone or summary bar chart, an S-curve, key variances, and the schedule narrative; working teams need detailed activity-level views. The schedule narrative is the standard vehicle: status date, work accomplished in the period, forecast for the next period, critical path and near-critical paths, float position, variances against baseline, risks and issues, and corrective actions.
Communicating honestly
Report uncertainty rather than false precision. Flag critical-path changes, baseline revisions, and float erosion early and to the right level; escalate per agreed thresholds. Protect schedule data confidentiality and control distribution of commercially sensitive dates. Capture communications in the plan and record significant schedule discussions and decisions. Confirm understanding, and reconcile conflicting reporting demands before they produce two versions of the truth.
Traps
- Sending detailed activity data to executives and one-line summaries to delivery teams.
- Assuming more data equals better communication.
- Announcing a rebaselined schedule without stating that the baseline changed.
- Reporting only percent complete and hiding critical-path movement.
- Confusing reporting frequency with reporting need.
Rule of thumb
One page, one headline: every schedule report should let the reader state within ten seconds whether the project is ahead, on track, or behind, and what the single most important reason is. Detail is appendix material supporting that headline.