I.7 — Help Ensure Knowledge Transfer

I.7 · Last updated: 11/10/2026

Knowledge transfer needs an environment as well as a record

I.7 — Help Ensure Knowledge Transfer is the seventh task in the People domain of the 2026 ECO, a domain that carries 33% of the exam. With only three enablers, it is one of the most narrowly defined tasks in the domain:

• Identify knowledge critical to the project
• Gather knowledge
• Foster an environment for knowledge transfer

The third item sets the character of the task. The first two describe actions, while the third describes a condition. The ECO does not regard gathering knowledge as enough on its own, so building an environment in which the knowledge can actually pass from person to person becomes part of the task as well.

The old I.7 moved to another domain

In 2026 this number did more than change its subject, since its old subject also left the domain. In 2021, I.7 was about addressing and removing impediments, obstacles, and blockers for the team. That topic is now III.4 — Remove Impediments and Manage Issues, which belongs to the Business Environment domain. In 2026, I.7 means knowledge transfer.

That sets a double trap for anyone planning their study time. An old question tagged "I.7" is most likely about impediments, and because the topic has also changed domain, someone who builds a study plan around the domain weights ends up charging those questions to the wrong domain's budget. Domain I came down to eight tasks while the old numbers ran to at least I.12, so collisions of this kind are spread across the whole domain. Match older material by its title and ignore the number; the general picture of the trap is in what changed in the 2026 PMP exam.

The PMBOK counterpart is Manage Project Knowledge

The Guide places this work in the Governance performance domain, as a process of the executing focus area (PMBOK® 8, Guide p.9). Manage Project Knowledge is the process of utilizing existing knowledge, including lessons learned, and creating new knowledge to achieve project objectives, enhance decision-making, and contribute to organizational learning (PMBOK® 8, Guide p.17).

The book sets out the process's two key benefits separately (PMBOK® 8, Guide p.24). The first is drawing on the organization's prior knowledge to produce or improve the project's outcome. The second is collecting the new knowledge the project creates so it can support organizational operations and future projects.

Read side by side, the two benefits show that knowledge management is no one-way record-keeping job, because a project both consumes knowledge and produces it. The enabler about identifying knowledge critical to the project corresponds to the first direction, and the one about gathering knowledge to the second.

Explicit and tacit knowledge

The basic distinction the exam relies on in this task is the one between two kinds of knowledge. According to the book, knowledge management deals with both explicit and tacit knowledge, and it does so for two purposes, reusing existing knowledge and creating new knowledge. The core activities beneath both purposes are knowledge sharing and integration, meaning that knowledge from different domains, contextual knowledge, and project management knowledge are brought together (PMBOK® 8, Guide p.24).

Explicit knowledge is formal and systematic. It can be readily codified in words, pictures, or numbers, and it is easily shared through information management tools such as databases, registers, and web searches (PMBOK® 8, Guide p.24).

Tacit knowledge behaves quite differently. The book describes it through four characteristics (PMBOK® 8, Guide p.25). It is personal and embedded, living in an individual's mind. It is difficult to articulate in words or documents. It is experience-based, resting on insights, experiences, and practical skills. And for all those reasons it is challenging to transfer, since it cannot be easily passed on to others.

Those four characteristics also explain why the ECO adds a separate enabler about the environment. Tacit knowledge cannot be carried by writing it into a document. It passes between people while they work together.

Turning tacit knowledge into explicit knowledge

The book states its goal here plainly: an important objective of knowledge management is converting tacit knowledge into explicit knowledge when possible (PMBOK® 8, Guide p.26). The qualifier "when possible" matters, because the book does not claim that every piece of tacit knowledge can be codified. For the knowledge that can be converted, it asks for three concrete decisions (PMBOK® 8, Guide p.26):

• Determining how and when lessons learned and retrospectives will be conducted throughout the project
• Identifying which information should be collected, both during the project and at its closure
• Establishing how historical information and lessons learned will be made available to current and future projects

All three give substance to the enabler about gathering knowledge, and all three are decisions to make at the start of the project. If you wait until closure to collect knowledge, a good part of it will already have been lost, since by then the team is beginning to disperse.

The tools for gathering knowledge

The tool list of the Manage Project Knowledge process is instructive in this respect (PMBOK® 8, Guide p.25). It includes after-action reviews, in-progress postmortems, storytelling, and retrospective meetings. Added to these are knowledge management and information management tools, together with interpersonal skills such as active listening, facilitation, leadership, networking, and political awareness. The outputs of the process include the lessons learned register and organizational process asset updates.

Two tools on that list stand out. Storytelling being counted as a formal tool is no accident, because elsewhere the book says stories are particularly effective for transferring tacit knowledge, which is hard to articulate through formal documentation (PMBOK® 8, Guide p.201). The in-progress postmortem, as its name suggests, carries out the analysis while the project is still running, so nothing waits for the end.

The lessons learned register that these tools feed is a project document or repository used to record the knowledge gained during a project, phase, or iteration so that it can improve the future performance of the team and the organization. Lessons from earlier projects can be used in the current one and are finally added to the organization's lessons learned repository (PMBOK® 8, Guide p.123).

Why the environment is an enabler of its own

The third enabler asks for a condition, and no document can satisfy it: fostering an environment for knowledge transfer. The Standard describes how such an environment is built. When the project management team promotes a culture of continuous improvement and reflective practice, it helps ensure that lessons learned are captured and shared, which enhances the team's collective expertise (PMBOK® 8, Standard p.31).

The precondition for that culture is trust. For an empowered project culture, the project environment needs to promote mutual trust among stakeholders and team members (PMBOK® 8, Standard p.53). Tacit knowledge does not get shared where trust is missing, and a mistake nobody talks about yields no lesson for anyone.

The Guide closes the loop with the result. When valuable insights are captured, shared, and utilized through these mechanisms, project outcomes improve and continuous improvement is driven forward (PMBOK® 8, Guide p.26).

Where the transferred knowledge flows

What this task produces becomes an input to two other tasks. On the continuous improvement side, utilizing lessons learned and updating organizational process assets are the enablers of a separate task; see III.6 — Continuous Improvement. On the closure side, the Close Project or Phase process includes archiving knowledge among the activities it finalizes (PMBOK® 8, Guide p.17); see II.10 — Manage Project Closure.

That is why an option saying lessons learned will be collected at the end of the project counts as wrong on the exam. The book turns that approach down explicitly, both by listing the in-progress postmortem as a tool and by asking for an early decision on how and when lessons will be gathered throughout the project.

About the citations

Every page number above refers to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked "ECO" separately.

⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:

• The Standard for Project Management — cited as Standard p. X
• A Guide to the Project Management Body of Knowledge — cited as Guide p. X

This page cites both books; which number belongs to which book is stated in every citation. The numbers are the books' printed page numbers.

This page describes the book; it does not replace it.