Communication and Knowledge Transfer

PMP PMP · People

By Abu Anns · Last updated 20 November 2026Exam version: July 2026 ECO (current since 9 July 2026)

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.

Advertisement

Exam traps to watch for

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?

Report an error

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?

Report an error

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?

Report an error

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?

Report an error

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?

Report an error

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?

Report an error

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?

Report an error

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?

Report an error