Manage Communications
Introduction: Why This Matters
Communication is the lifeblood of projects. Research consistently shows that poor communication is one of the leading causes of project failure. As a project manager, you must ensure that the right information reaches the right people at the right time, in the right format. Effective communication builds trust, reduces misunderstandings, and aligns stakeholders with project goals.
On the PMP Exam, communication scenarios are common. The correct answers typically focus on proactive planning, transparency, tailoring communication to stakeholder needs, and maintaining two-way information flow, not just broadcasting updates.
Purpose and Objectives
Primary Purpose: Create and maintain a communication framework that keeps all parties informed, engaged, and aligned.
Key Objectives:
- Develop and execute a project communication plan.
- Tailor communication methods to diverse stakeholder needs.
- Ensure transparency through regular reporting and feedback loops.
- Leverage tools and technologies to streamline communication.
- Prevent misalignment by maintaining consistency and clarity.
Overview
Managing project communications means intentionally planning, delivering, and adapting how information flows across stakeholders so alignment stays strong and surprises stay rare.
- What you are managing: Frequency, format, detail level, and channels for project information.
- What “good” looks like: Stakeholders are informed at the right level, feedback is captured, and trust stays intact.
Characteristics
- Tailored delivery: Executives get high-level dashboards; delivery teams get detailed execution updates.
- Appropriate methods: Interactive for complex topics, push for routine updates, pull for reference material.
- Transparency: Issues are surfaced early with options, impacts, and next actions.
- Two-way flow: Feedback loops exist so communication becomes collaboration.
- Consistent artifacts: Reports, dashboards, and updates stay reliable and predictable.
Practical Example
Context: An IT project rolling out a new student portal faced stakeholder frustration because updates were too technical for non-technical audiences.
Activities:
- Executive visibility: Created a dashboard with key performance indicators for scope, schedule, and risks.
- Team alignment: Held weekly progress standups with the technical team.
- Broad engagement: Hosted monthly town halls for faculty and student representatives.
Outcome: Stakeholders understood progress at the right level of detail, engagement increased, and resistance dropped significantly.
Common Pitfalls
Pitfall Category One: Mismatched detail and timing
- Pitfall: Overloading stakeholders with irrelevant details, causing disengagement and missed signals.
- Prevention: Tailor by influence, interest, and preference. Use dashboards and summaries for leaders, and deeper reports for delivery teams.
Pitfall Category Two: Avoiding hard conversations
- Pitfall: Failing to communicate bad news promptly, eroding trust.
- Prevention: Communicate early with impact, options, and recommended next actions.
Pitfall Category Three: One-way broadcasting
- Pitfall: Over-reliance on email and neglecting feedback loops, turning communication into a monologue.
- Prevention: Use interactive methods for complexity and establish feedback mechanisms such as one-on-ones, surveys, and retrospectives.
Sensei Tip : If a stakeholder says they are “surprised,” your communication plan has a gap. Fix the plan, then stabilize the cadence.
Exam Alert : The PMP Exam often punishes “just send an email” answers. When the issue is alignment, clarity, or surprise, the best move is usually to revise and tailor the communication plan and restore a reliable feedback loop.
Exam Lens
Patterns on the PMP Exam:
- Choose answers that emphasize tailored communication, transparency, and proactive planning.
- Prefer two-way communication and stakeholder alignment over broadcasting updates.
- Avoid answers that delay reporting, shift responsibility to the team, or ignore sponsor preferences.
Sample Question
Question: A sponsor complains that they are surprised by project delays. What should the project manager do?
- Increase the frequency of technical team meetings.
- Revise the communication plan to include timely, tailored updates for the sponsor.
- Wait until the next phase review to share performance reports.
- Ask the team to provide updates directly to the sponsor.
Correct Answer: B. Revise the communication plan to include timely, tailored updates for the sponsor. Explanation: The issue is stakeholder surprise, which signals the sponsor is not receiving the right information at the right time. The project manager owns the communication framework and should tailor cadence and format for the sponsor. Increasing technical meetings, delaying reports, or delegating sponsor updates does not resolve the root cause.
Quick Recap Table
| Concept | Description | Exam Watch Point |
|---|---|---|
| Communication Methods | Interactive, push, pull | Choose based on stakeholder needs and complexity |
| Tailoring | Adjust to role, influence, interest, and preference | Avoid one-size-fits-all updates |
| Transparency | Share successes and challenges early | Exam rewards honesty, clarity, and options |
| Feedback Loops | Two-way communication and stakeholder input | Prevents surprises and disengagement |
| Pitfalls | Overload, hiding bad news, ignoring feedback | Avoid “broadcast only” habits |
Key Takeaways
- Communication is a structured process, not an afterthought.
- Tailoring is essential. Different stakeholders require different levels of detail and delivery methods.
- Transparency builds trust, while hiding problems erodes it quickly.
- Feedback loops turn communication into collaboration and prevent surprise escalations.
- Exam scenarios reward proactive, inclusive, and tailored approaches.
Next Step
Next, we move to Task 3: Assess and Manage Risks, where you will learn how to identify, analyze, prioritize, and respond to risks in order to protect value delivery.
Bibliography
Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.