Communication and Knowledge Transfer
PMP PMP · People
Communication is the project manager's main job
Project managers spend the majority of their time communicating — with the team, the sponsor, stakeholders, vendors, and executives. The July 2026 ECO gives this two tasks in the People domain: plan and manage communication, and help ensure knowledge transfer. The exam tests communication as a practical skill: choosing the right method for the message, listening actively, managing the flow of information so the right people know the right things at the right time, and making sure knowledge created on the project is not lost when the project ends.
The starting point is the communications management plan, which is created during planning and answers a simple set of questions for each type of information: who needs it, what do they need, when do they need it, in what format, and through which channel? A status report for the sponsor looks different from a technical update for the team, and both look different from a regulatory filing. The exam tests whether you tailor communication to the audience: sending a 40-page technical report to an executive who needs a one-page summary is a communication failure, even if the report is accurate.
Communication methods and channels
PMI classifies communication methods in several ways that the exam tests. Interactive communication (meetings, video calls, phone calls) involves two or more people exchanging information in real time and is the best method for complex, sensitive, or ambiguous messages — because misunderstandings can be caught and corrected immediately. Push communication (emails, reports, memos) sends information to specific recipients who need to know it, but the sender cannot be sure it was received or understood. Pull communication (intranet sites, shared repositories, knowledge bases) makes information available for people to access when they need it, and is best for large volumes of information that different people need at different times.
The choice of method is a common exam scenario. A sensitive message — telling a team their work will be restructured, or informing a stakeholder of a serious delay — should be delivered interactively, face to face or by video, not by email. A routine status update is fine as push communication. A project archive is a pull resource. When a question describes a communication failure, the cause is often the wrong method: an email sent where a conversation was needed, or a meeting held where a short message would have done.
The exam also tests the communication channels formula, one of the few formulas in the People domain: the number of communication channels between n people is n(n-1)/2. With 5 people there are 10 channels; with 10 people there are 45; with 20 people there are 190. The point is not the arithmetic for its own sake but the insight behind it: communication complexity grows much faster than team size, which is why large projects need structured communication plans and why adding people to a late project often makes it later. A question might ask how many channels exist after two people join a team of 8: the team becomes 10 people, so the channels go from 28 to 45.
Active listening and feedback
Communication is a two-way process, and the exam places as much weight on listening as on speaking. Active listening means giving the speaker your full attention, acknowledging what they say, asking clarifying questions, and paraphrasing back what you heard to confirm understanding — "So what you're saying is that the deadline is achievable if we drop the reporting module. Is that right?" This is not politeness for its own sake; it is how misunderstandings are caught before they become expensive mistakes. Many exam scenarios describe a project manager who assumed they understood a requirement, only to discover late that they did not. The correct action in hindsight is always active listening and confirmation.
Feedback follows the same principles as in the team leadership guide: specific, timely, focused on behavior and its impact, and delivered in a way the recipient can act on. In communication terms, the exam also tests the feedback loop: the sender encodes a message, the receiver decodes it, and noise — anything that distorts the message, from technical jargon to cultural differences to a bad phone connection — can corrupt it at any stage. The project manager's job is to reduce noise and confirm receipt: ask the receiver to summarize what they understood, especially for important or complex messages.
Managing communications during the project
Planning communication is only half the task; managing it during execution is where the exam's situational questions live. Common scenarios include: stakeholders complaining they are not kept informed (the fix is to review and adjust the communications plan, not to send more emails at random); team members in different locations misunderstanding each other (the fix is to clarify channels and expectations, and to prefer interactive communication for complex topics); and information overload, where people stop reading updates because there are too many (the fix is to reduce frequency and improve relevance, not to add more channels).
Cultural and language differences deserve special attention. In international projects, directness, attitudes to hierarchy, and the meaning of silence vary widely, and the exam expects cultural sensitivity: adapt your communication style to your audience, avoid idioms and jargon that may not translate, confirm understanding explicitly, and never assume that silence means agreement. A question describing a team member from another culture who does not speak up in meetings is usually testing whether you would create safer ways for them to contribute — for example, asking for input in writing before the meeting — rather than concluding they have nothing to say.
Knowledge transfer: making sure learning survives the project
The second task in this guide — help ensure knowledge transfer — is about making sure what the project learns does not leave with the people who learned it. Knowledge comes in two forms. Explicit knowledge can be written down: procedures, designs, test results, lessons learned. Tacit knowledge lives in people's heads: judgment, experience, the reasons behind decisions, the things that did not work and why. Explicit knowledge is transferred through documents, repositories, and training; tacit knowledge is transferred through mentoring, pairing, shadowing, and conversation. The exam tests both: a question about a key team member leaving the project is testing whether you would arrange knowledge transfer before they go — pairing them with a successor, documenting their knowledge, and recording the reasoning behind key decisions.
Lessons learned are the main vehicle for knowledge transfer between projects. They are captured throughout the project, not just at the end — waiting until closure means the lessons of the early phases are forgotten. The lessons learned register records what went well, what went badly, and what the organization should do differently next time, and it feeds the organizational process assets that future projects draw on. At project closure, the project manager ensures the register is complete and accessible, and that the knowledge is shared with the wider organization through retrospectives, reports, or presentations.
Exam mindset for communication
For communication questions, the pattern is familiar: understand the audience and the message, choose the method that fits, confirm understanding, and adjust when communication fails. Interactive communication for sensitive or complex messages, push for routine updates, pull for reference information. Active listening whenever understanding matters — which is almost always. And for knowledge transfer, the rule is simple: capture knowledge continuously, transfer it before people leave, and make sure the next project can find it.
Exam traps to watch for
- Sending a sensitive or complex message by email. Interactive communication (face to face or video) is the right method when misunderstanding is likely or feelings are involved.
- Forgetting the channels formula or misapplying it: channels = n(n-1)/2, where n is the number of people — and the question may ask for the change after people join or leave.
- Capturing lessons learned only at project closure. Lessons are recorded throughout the project; waiting until the end means early lessons are lost.
- Assuming silence means agreement, especially across cultures. Confirm understanding explicitly; silence can mean disagreement, confusion, or politeness.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A project has 8 stakeholders who all need to communicate with each other. Two more stakeholders join the project. How many communication channels are there now?
Explanation: The communication channels formula is n(n-1)/2, where n is the number of people. With the two new stakeholders, n = 10, so the channels are 10 x 9 / 2 = 45. Option B (36) is the result for 9 people (9 x 8 / 2 = 36) — it counts only one of the two new stakeholders. Option D (28) is the number of channels before the new stakeholders joined (8 x 7 / 2 = 28). Option C (90) is the result of forgetting to divide by 2 (10 x 9 = 90).
Exam objective: PMP ECO Task: Plan and manage communication (People)
Q2.A project manager must inform a key stakeholder that the project will be delayed by six weeks. What is the BEST way to deliver this news?
Explanation: Bad news about a significant delay is sensitive and complex: the stakeholder will have questions, concerns, and possibly strong feelings, and the project manager needs to read their reaction and respond in real time. Interactive communication — face to face or by video — is the right method. Option D is wrong because email cannot handle the stakeholder's reaction, and important news delivered by email often reads as evasive. Option B is wrong because posting bad news on a shared page is impersonal and denies the stakeholder a chance to discuss it. Option C is wrong because withholding bad news for two weeks destroys trust; stakeholders should hear about problems from the project manager, promptly, not discover them later.
Exam objective: PMP ECO Task: Plan and manage communication (People)
Q3.Several stakeholders complain that they receive too many project emails and have stopped reading them. As a result, one stakeholder missed an important decision deadline. What should the project manager do?
Explanation: Information overload is a communication failure, and the fix is to tailor communication to the audience: review the communications plan with the stakeholders, find out what each of them actually needs, and adjust frequency, format, and content accordingly — for example, a short weekly summary for executives instead of daily detail. Option C is wrong because more emails make overload worse. Option A is wrong because forcing stakeholders onto a portal they must check daily replaces one burden with another and removes the push notifications that flag time-sensitive items. Option B is wrong because the stakeholders are not the problem — the communication approach is — and escalation would damage relationships without fixing anything.
Exam objective: PMP ECO Task: Plan and manage communication (People)
Q4.A project manager is discussing requirements with a customer. After the customer explains a complex requirement, the project manager says: 'So you need the report to update automatically each morning and to include data from all three regions. Have I understood that correctly?' What is the project manager doing?
Explanation: Paraphrasing what the speaker said and asking for confirmation is active listening: it checks that the message received matches the message sent, and it catches misunderstandings at the cheapest possible moment — during the conversation, not after the work is built. Option A is wrong because push communication is one-way distribution of information (emails, reports), not a two-way confirmation. Option C is wrong because confirming understanding is taking responsibility for getting it right, not avoiding it. Option B is wrong because this is a spoken exchange, not formal written communication.
Exam objective: PMP ECO Task: Plan and manage communication (People)
Q5.A senior engineer who holds critical knowledge about the project's legacy system announces they will leave the organization in three weeks. What should the project manager do FIRST?
Explanation: Knowledge transfer has to happen before the knowledge walks out the door, and it needs both forms of knowledge: explicit knowledge (documents) and tacit knowledge (judgment, reasoning, experience), which is transferred through pairing and conversation. Three weeks is enough time for a structured handover if it starts immediately. Option D is weaker because a manual alone captures only explicit knowledge — it does not transfer the engineer's judgment or the reasons behind decisions, and a rushed manual is often incomplete. Option C is wrong because a new hire learning on the job after the expert has left will take months to reach the same understanding, and some knowledge will be lost permanently. Option A is wrong because it depends on the engineer accepting, does not solve the underlying single-point-of-failure problem, and is a human resources matter, not the project manager's first move.
Exam objective: PMP ECO Task: Help ensure knowledge transfer (People)
Q6.A team member from another country rarely speaks in meetings, and the project manager is unsure whether they agree with the decisions being made. What is the BEST action?
Explanation: Silence does not mean agreement — in many cultures, speaking up in a group, especially to disagree with a senior person, is uncomfortable or inappropriate, and language barriers can add to the difficulty. The project manager's job is to create channels where this person can contribute comfortably: written input before meetings, smaller discussions, and one-to-one check-ins. Option B is wrong because assuming agreement from silence is exactly how misunderstandings become expensive mistakes. Option D is wrong because putting someone on the spot publicly increases their discomfort and is unlikely to produce honest input. Option A is wrong because excluding the team member wastes their knowledge and signals that their contribution is not valued.
Exam objective: PMP ECO Task: Plan and manage communication (People)
Q7.A project is in its third month when the project manager realizes that lessons learned have not been recorded since the project started. What should the project manager do?
Explanation: Lessons learned are captured throughout the project, not only at closure — and it is never too late to start. The project manager should begin now, run a session to recover what the team can still remember from the first three months, and make continuous capture part of the project's routine (for example, in retrospectives or phase reviews). Option A is wrong because waiting until closure means more lessons will be forgotten, and the lessons captured will be too late to help this project. Option C is wrong because giving up wastes the learning that is still recoverable and deprives future projects of it. Option D is wrong because it repeats the same mistake — deferring capture to the end — and individual reports written months later will be incomplete.
Exam objective: PMP ECO Task: Help ensure knowledge transfer (People)
Q8.A project manager needs to share the project's technical design documents with 50 engineers across five teams. Each engineer needs different sections at different times. Which communication method is MOST appropriate?
Explanation: Pull communication is designed for exactly this situation: a large volume of information that different people need at different times. A shared repository lets each engineer find the sections they need when they need them, without flooding anyone's inbox or forcing everyone into a meeting. Option D is wrong because a meeting with 50 people to walk through documents is an enormous waste of time, and most attendees would not need most of the content. Option B is wrong because emailing the full document set to everyone creates information overload and version-control problems. Option C is wrong because printed documents go out of date immediately and cannot be searched or updated centrally.
Exam objective: PMP ECO Task: Plan and manage communication (People)