I.7 — Help Ensure Knowledge Transfer

I.7 · Last updated: 24/08/2026

Where this task sits

I.7 — Help Ensure Knowledge Transfer is the seventh task in the People domain of the 2026 ECO. The domain carries 33% of the exam.

It has only three enablers — the fewest in the domain:

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

The third one defines this task's character. The first two are actions; the third is a condition. The ECO does not consider gathering knowledge sufficient — it puts the environment in which transfer happens inside the task too.

🔴 Do not trust the number

This number changed hands entirely in 2026, and its old subject went to another domain:

• In 2021, I.7 was address and remove impediments, obstacles, and blockers for the team. In 2026 that topic is III.4 — Remove Impediments and Manage Issues, and it now lives in the Business Environment domain.
• In 2026, I.7 is knowledge transfer.

So an older question tagged "I.7" is most likely about impediments — and because the topic changed not just number but domain, anyone building a study plan around domain weights gets it wrong twice.

The collision shows up in practice: the same "I.7" tag can appear on both impediment and knowledge-transfer questions in off-the-shelf banks. Since Domain I came down to eight tasks in 2026 (older numbers ran at least as far as I.12), collisions like this are common across the domain.

Match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.

The PMBOK counterpart: Manage Project Knowledge

The Guide ties this work to a process in the Executing focus area of the Governance performance domain.

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 process's two key benefits are stated separately (PMBOK® 8, Guide p.24):

• Using prior organizational knowledge to produce or improve the project outcome, and
• Collecting new knowledge created by the project to support organizational operations and future projects or phases.

Read them together: knowledge management is not a one-way recording job. A project both consumes knowledge and produces it. The ECO's "identify knowledge critical to the project" enabler is the first direction; "gather knowledge" is the second.

Explicit knowledge versus tacit knowledge

The fundamental distinction on this task, and the book describes each separately.

Knowledge management is concerned with managing both explicit and tacit knowledge for two purposes: reusing existing knowledge and creating new knowledge. The key activities underpinning both are knowledge sharing and integration — incorporating knowledge from different domains, contextual knowledge, and project management knowledge (PMBOK® 8, Guide p.24).

Explicit knowledge is formal and systematic; it is the type that can be readily codified (PMBOK® 8, Guide p.24).

Tacit knowledge has four key characteristics (PMBOK® 8, Guide p.25):

• Personal and embedded — resides within an individual's mind.
• Difficult to articulate — challenging to express in words or documentation.
• Experience-based — includes insights, experiences, and practical skills.
• Challenging to transfer — cannot be easily shared or communicated to others.

Those four explain why the ECO adds a separate "environment" enabler: tacit knowledge cannot be transferred by writing it into a document — it passes between people.

The real objective: converting tacit into explicit

The book's clearest statement of purpose here: an important objective of knowledge management is converting tacit knowledge into explicit knowledge when possible (PMBOK® 8, Guide p.26).

The "when possible" qualifier matters — the book does not claim all tacit knowledge can be codified. But for what can be, 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 benefit the current project and future projects.

All three fill in the ECO's "gather knowledge" enabler — and all three are decisions made in advance. Knowledge you try to collect at closure may already be gone.

Tools: how knowledge is gathered

The tools of the Manage Project Knowledge process make a notable list (PMBOK® 8, Guide p.25):

After-action reviews (AARs), in-progress postmortems, storytelling, and retrospective meetings — alongside knowledge management, information management, and interpersonal and team skills: active listening, facilitation, leadership, networking, and political awareness.

The process outputs are the lessons learned register and organizational process asset updates (PMBOK® 8, Guide p.25).

Two details stand out. First, storytelling counted as a formal tool — narrative is one of the ways tacit knowledge moves. Second, the in-progress postmortem: analysis while the project is still running, not at the end.

The lessons learned register is a project document or repository used to record knowledge gained during a project, phase, or iteration so it can improve future performance for the team and the organization; lessons from previous projects can be used in the current one and entered into the lessons learned repository (PMBOK® 8, Guide p.123).

Why "environment" is its own enabler

The ECO's third enabler asks not for a document but for a condition: foster an environment for knowledge transfer.

The Standard says how that gets built: by promoting a culture of continuous improvement and reflective practice, the project management team helps ensure that lessons learned are captured and shared, enhancing the team's collective expertise (PMBOK® 8, Standard p.31).

The condition on the culture side is trust: for an empowered project culture, the project environment should promote mutual trust among stakeholders and team members (PMBOK® 8, Standard p.53). Tacit knowledge is not shared where trust is absent — a mistake nobody recounts teaches nobody anything.

The Guide ties off the consequence: valuable insights being captured, shared, and utilized enhances project outcomes and drives continuous improvement (PMBOK® 8, Guide p.26).

Where knowledge transfer gets used

This task does not stand alone; what it produces is 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.

Translated for the exam: the option saying "we will collect lessons learned at the end of the project" is wrong. By asking for both in-progress postmortems and a decision on "how and when throughout the project," the book rejects it outright.

About the citations

The page numbers above refer to the PMBOK® Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked as "ECO."

⚠️ 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 explains the book; it does not replace it.