"90% of project management is communication." — PMI. Giao tiếp hiệu quả ngăn ngừa 80% vấn đề dự án. PM phải plan, execute và monitor communication proactively.
📖 Communication Formula & Key Concepts
🇺🇸 English
Communication channels formula: n(n-1)/2 where n = number of stakeholders. 5 people = 10 channels; 10 people = 45 channels. Adding people to a project exponentially increases communication complexity.
Communication models:
Sender → Message → Medium → Receiver → Feedback
Noise can disrupt at any stage (technical, semantic, cultural)
PM is responsible for effective communication, not just sending information
Công thức kênh giao tiếp: n(n-1)/2 với n = số stakeholders. 5 người = 10 kênh; 10 người = 45 kênh. Thêm người vào dự án tăng độ phức tạp giao tiếp theo cấp số nhân.
Loại giao tiếp:
Interactive: Hai chiều, real-time (họp, gọi điện)
Push: Một chiều gửi đi (email, báo cáo)
Pull: Người nhận tự lấy (wiki, Confluence, shared drive)
🔧 Communication Management Plan Template
Stakeholder
Information Needed
Format
Frequency
Owner
Channel
Project Sponsor
Executive status, risks, decisions needed
1-page executive summary
Weekly (Monday)
PM
Email + Slack
Bank Partner A
Integration progress, API changes, go-live date
Formal progress report
Bi-weekly
PM
Email + Video call
Dev Team
Sprint goals, blockers, priority changes
Sprint planning, daily standup
Daily + bi-weekly planning
PM/SM
Jira, Slack, Zoom
QA Team
Test schedules, bug priorities, release readiness
QA report
Weekly
QA Lead
Jira, Slack
Steering Committee
Project health, milestone status, major issues
Dashboard + verbal briefing
Monthly
PM
Meeting + Slides
📊 Information Radiators (Agile)
🇺🇸 English
Information radiators (Big Visible Charts) are large, visible displays that passively communicate project status. Examples: sprint burndown chart, kanban board, velocity chart, impediment board.
The principle: information should be pull (always available, self-serve) rather than push (PM sends reports). This reduces communication overhead and increases transparency.
Information radiators là màn hình hiển thị lớn, visible, giao tiếp passively trạng thái dự án. Ví dụ: sprint burndown chart, kanban board, velocity chart.
Nguyên tắc: thông tin nên là pull (luôn sẵn có, tự phục vụ) thay vì push (PM gửi báo cáo).
🎯
Exam Tips — Communications
Communication plan = FIRST thing PM creates for stakeholder communication
Formula: n(n-1)/2 — memorize this for calculation questions
PM is responsible for effective communication — not just sending. Verify understanding.
Informal, face-to-face = most effective for complex discussions
Written communication = for formal records, complex information, large audience
Agile: information radiators replace many formal reports — information is ALWAYS visible
💼 Thực chiến / Scenario
🏢
FinTech Company X — Communication Failure Avoidance
Tình huống: Project Alpha sprint 3 kết thúc. PM gửi email status report cho sponsor, nhưng sponsor xuất hiện trong all-hands meeting và complain rằng họ "không biết" về 2-week delay trong partner integration.
Root cause: Email không phù hợp cho thông tin quan trọng như delay. Sponsor cần interactive communication để process và respond. Email là push communication — không verify understanding.
Corrective action: PM cập nhật Communication Management Plan: Critical risks/delays → báo cáo ngay qua Slack + follow-up call trong 24h. Weekly Slack update được replace bằng 30-minute Friday call với sponsor. Biên bản meetings được documented và sent for review.
PMP lesson: Match communication medium to message importance. Tạo communication plan sớm trong project — đừng improvise.
🗂️ Communication Management Plan — Quick Reference
Communication Management Plan — Quick Reference
── STAKEHOLDER COMMUNICATION MATRIX ────────────────StakeholderInfo NeededChannelFrequencyFormatOwnerSponsor Executive summary, RAG Slack + Email Weekly 1-page exec summary PM
status, key risks, decisions
needed
Dev Team Sprint goals, blockers, Jira + Slack Daily Standup / sprint plan PM / SM
priority changes
Partner Bank A Integration progress, Video + Email Bi-weekly Progress report PM
API changes, go-live date
Steering Cmte Project health, milestone Deck + Meeting Monthly Dashboard + briefing PM
status, major issues
── KEY PRINCIPLES ──────────────────────────────────Match medium to message importance — critical issues = interactive (call/meeting)
Tailor content to audience — executives need summary, team needs detail
Verify understanding — communication is not just sending, it's received + understood
✏️ Practice Questions
Question 1
A project team is adding 3 new members, bringing the total to 8 people. How many additional communication channels will be created?
A. 6
B. 15
C. 17
D. 28
✅ Answer: C (17) Before (5 people): 5(5-1)/2 = 10 channels After (8 people): 8(8-1)/2 = 28 channels Additional: 28 - 10 = 17 new channels
Question 2
Which is MOST effective for communicating a complex technical change that requires discussion and immediate stakeholder response?
A. Email with detailed documentation attached
B. Posted notice on project wiki
C. Interactive meeting with all affected stakeholders
D. Formal written memo to all stakeholders
✅ Answer: C — For complex information requiring discussion and immediate response, interactive (two-way, real-time) communication is most effective. The other options are push or pull (one-way) communication that don't allow immediate discussion and questions.
Question 3
A PM sends a detailed technical email to the project sponsor every week. The sponsor replies saying they don't have time to read it. What should the PM do?
A. Stop sending reports to the sponsor
B. Convert to a 1-page executive summary with RAG status, key metrics, and decisions needed — matching the sponsor's information needs and attention
C. Send a shorter version of the same technical email
D. Ask another team member to write the report
✅ Answer: B — The PM is responsible for effective communication, not just sending information. The sponsor is a high-influence stakeholder who needs executive-level summaries, not technical detail. Adapting the communication format to match the audience's needs (RAG status, key metrics, decisions needed) is the correct PMI approach. Stopping reports (A) leaves the sponsor uninformed. A shorter technical email (C) still mismatches the audience. Delegating (D) does not address the root cause.
🤖 AI Tools for PMs
🤖
How AI Augments This Process
AI helps PMs draft stakeholder-tailored communications, create communication plans, generate meeting agendas, and adapt messaging tone for different audiences and channels.
Sample Claude Prompts
Stakeholder-tailored message drafting
I need to communicate [announcement / decision / project update] to multiple stakeholder groups.
The core message: [what I need to convey]
Stakeholder groups and their characteristics:
Group 1: [Executives] — care about [business impact, risk, ROI]
Group 2: [Technical team] — care about [how it works, technical implications]
Group 3: [End users] — care about [how it affects their daily work]
Group 4: [External partners] — care about [contractual impact, timelines]
Draft 4 versions of this communication, each tailored to:
- The audience's primary concern
- Their preferred level of detail
- The appropriate tone and vocabulary
- The specific call to action for each group
Keep each version under 200 words.
Communication plan creation
Create a Communication Management Plan for my project.
Project: [name and brief description]
Project phase: [planning / execution / close]
Key stakeholders: [list with roles and interest level]
Key communications needed:
- [Type of update — frequency — audience — purpose]
- [Meeting name — cadence — participants — decision-making or informational?]
Generate a Communication Plan table with:
1. Communication item, purpose, frequency, format, sender, audience, channel
2. Escalation communication triggers (when to send unplanned communications)
3. Sensitive topics communication protocol (bad news, scope changes)
4. Communication calendar for next 4 weeks
Also flag: which stakeholders are currently under-communicated with?
Bad news communication drafting
I need to communicate bad news to [stakeholder / team / sponsor].
The news: [what happened — delay / cost overrun / quality issue / missed commitment]
Root cause: [brief — don't make excuses, just facts]
Impact: [what this means for the project]
What we're doing about it: [corrective action plan]
What I need from them: [decision / support / patience]
Draft a communication that:
1. Opens directly with the news (no burying the lede)
2. Takes appropriate accountability without over-apologizing
3. Focuses on the forward plan (what happens next)
4. Specifies a clear next step or ask
5. Maintains stakeholder confidence despite the setback
Also: what should I NOT say (common PM mistakes in bad news comms)?
Jira / Confluence Template
Confluence — Communication Plan
── CONFLUENCE: COMMUNICATION MANAGEMENT PLAN ────────────Project: [Project Alpha] | PM: [name] | Last updated: [date]
── COMMUNICATION MATRIX ──────────────────────────────────
What | Who | How | When | Owner
─────────────────────|───────────────────|───────────────|─────────────|──────
Weekly status report | Sponsor + Steering | Email/Confluence | Every Monday | PM
Sprint review demo | Product + Business | Video call | End of sprint| PO + PM
Risk register update | PMO | Confluence | Bi-weekly | PM
Technical update | Dev leads | Slack + 30min | Weekly | Tech Lead
Partner comms | Bank Partner A | Email | As needed | PM
── ESCALATION TRIGGERS ───────────────────────────────────
• Schedule slips >1 sprint → immediate sponsor notification
• Budget variance >10% → PMO escalation within 24h
• P0 production defect → partner + sponsor within 2 hours
• Team member exit → sponsor notification same day
── SENSITIVE TOPICS PROTOCOL ─────────────────────────────Bad news: Always verbal first (call/video), follow up in writing within 24h
Scope changes: CCB process — never by email announcement alone