Why Communication Is the PM's Most Important Skill
Project managers spend 75-90% of their time communicating. Communication is the connective tissue that holds a project together. Miscommunication causes misaligned expectations, duplicated effort, missed deadlines, and stakeholder frustration.
Communication Plan
| Communication | Audience | Frequency | Channel | Owner | Format |
|---|---|---|---|---|---|
| Daily Standup | Dev Team | Daily | Slack/Meeting | Scrum Master | 15-min sync |
| Sprint Review | Team + Stakeholders | Bi-weekly | Video call | PO | Demo + discussion |
| Status Report | Sponsor, Mgmt | Weekly | PM | RAG report | |
| Steering Committee | Executives | Monthly | Meeting | PM | Executive summary |
| Risk Review | PM, Tech Lead, PO | Bi-weekly | Meeting | PM | Risk register review |
| Release Notes | All stakeholders | Per release | Email + Wiki | PM | Written document |
RAG Status Report Template
// Weekly Status Report Data Model
interface StatusReport {
projectName: string;
reportDate: Date;
reportPeriod: string;
preparedBy: string;
overallStatus: 'green' | 'amber' | 'red';
statusAreas: {
area: string;
status: 'green' | 'amber' | 'red';
commentary: string;
}[];
accomplishments: string[];
plannedNextWeek: string[];
risks: { description: string; severity: 'high' | 'medium' | 'low'; mitigation: string }[];
issues: { description: string; impact: string; owner: string; dueDate: Date }[];
decisions: { description: string; decidedBy: string; date: Date }[];
metrics: {
sprintVelocity: number;
plannedVsActual: string;
budgetSpent: string;
budgetRemaining: string;
scopeComplete: string;
};
}
const weeklyReport: StatusReport = {
projectName: 'Mobile Commerce App v2.0',
reportDate: new Date('2024-06-14'),
reportPeriod: 'June 10-14, 2024',
preparedBy: 'Jordan Williams',
overallStatus: 'amber',
statusAreas: [
{ area: 'Schedule', status: 'amber', commentary: 'Sprint 5 velocity below target (28 vs 34 planned). Checkout flow taking longer than estimated.' },
{ area: 'Budget', status: 'green', commentary: 'On budget. $380K spent of $800K (47.5%). Month 3 of 7.' },
{ area: 'Scope', status: 'green', commentary: '62% of stories complete. On track for MVP milestone.' },
{ area: 'Quality', status: 'green', commentary: 'Zero critical bugs. Code coverage at 82%.' },
{ area: 'Resources', status: 'amber', commentary: 'iOS specialist needed for push notifications. Interviewing candidates.' }
],
accomplishments: [
'Product catalog search with Elasticsearch deployed to staging',
'Shopping cart persistence across sessions implemented',
'Performance testing framework set up with k6',
'Security audit of auth service completed — 2 medium findings addressed'
],
plannedNextWeek: [
'Complete checkout flow UI (Sprint 6 goal)',
'Begin payment gateway integration (Stripe)',
'Onboard iOS specialist (target start: June 17)',
'Load test shopping cart at 1000 concurrent users'
],
risks: [
{ description: 'Checkout flow complexity higher than estimated', severity: 'medium', mitigation: 'Simplify initial flow, defer Apple Pay to phase 2' },
{ description: 'iOS specialist hiring delayed', severity: 'high', mitigation: 'Engaging contract agency as backup' }
],
issues: [
{ description: 'Staging environment SSL cert expired', impact: 'QA blocked for 4 hours', owner: 'DevOps', dueDate: new Date('2024-06-14') }
],
decisions: [
{ description: 'Apple Pay deferred to phase 2 to protect timeline', decidedBy: 'Product Owner', date: new Date('2024-06-12') }
],
metrics: {
sprintVelocity: 28,
plannedVsActual: '28 / 34 points (82%)',
budgetSpent: '$380,000 (47.5%)',
budgetRemaining: '$420,000',
scopeComplete: '62% of user stories done'
}
};
RAG Status Definitions
- GREEN: On track. No significant issues. Current trajectory will meet objectives.
- AMBER: At risk. Issues exist that could impact delivery if not addressed. PM can resolve without executive intervention.
- RED: Off track. Significant issues that require executive intervention or scope/timeline changes.
Communication Best Practices
Golden Rules
- Tailor the Message: Executives want the headline and impact. Engineers want technical details. QA wants test results. Never send a one-size-fits-all update.
- Bad News Travels Fast: Deliver bad news immediately and in person. Never let stakeholders discover issues from someone else.
- Over-Communicate During Crises: During incidents or major issues, increase update frequency (hourly for critical, daily for high).
- Write for Scanning: Use bullet points, bold key items, and lead with the most important information. Nobody reads paragraphs.
- Document Decisions: Verbal decisions are forgotten. Follow up every meeting with written decisions and action items.