Knowledge Transfer: Do Not Let Expertise Leave with People

When an expert leaves a project, their tasks do not vanish — those are documented and assigned. What vanishes is everything that was never written: why that supplier was chosen over another, what was tried and failed two years ago, how to handle this particular customer. The Eighth Edition names these two kinds precisely and treats each differently, stating outright that managing knowledge involves more than just documenting explicit knowledge for sharing or obtaining lessons learned at the end of the project.

Definition and Foundation

Manage Project Knowledge is the process of using existing knowledge and creating new knowledge to achieve the project's objectives and contribute to organizational learning. Its key benefits: using prior organizational knowledge to produce or improve the outcome, and collecting new knowledge created by the project to support operations and future projects.

• Two purposes — knowledge management is concerned with managing both explicit and tacit knowledge for two purposes: reusing existing knowledge and creating new knowledge.
• Two activities underpinning them — the key activities that underpin both purposes are knowledge sharing and integration: incorporating knowledge from different domains, contextual knowledge, and project management knowledge.

Explicit knowledge is formal and systematic, readily codified in words, pictures, or numbers — manuals, procedures, documented processes — and easily shared through information management tools such as databases, registers, and web searches. It has three characteristics: codifiable in words, pictures, or numbers; formal and systematic, structured in a way that is easy to understand; and easily communicated through manuals, procedures, and other documentation.

Tacit knowledge is information embedded in a person's mind and highly personal, difficult to articulate because it consists of technical skills, experiences, insights, and practical knowledge, and challenging to formalize, which makes it hard to transfer to others or to different projects. It has four characteristics: personal and embedded, residing within an individual's mind; difficult to articulate in words or documentation; experience-based, including insights, experiences, and practical skills; and challenging to transfer, not easily shared.

How It Works in Practice

Why documentation is not enough

This is the key to the whole topic. The guide states that codified explicit knowledge lacks context and is open to different interpretations, so even though it is more easily shared, it is not always understood or applied in the right way. Tacit knowledge has further context but is difficult to codify. The trade-off is therefore not between a good kind and a poor one, but between one easy to move and thin on context, and one rich in context and hard to move. The practical decision is to use each kind's own medium: codification for the explicit, direct interaction for the tacit — and trying to move tacit knowledge with explicit-knowledge tools is the most common error here.

How tacit knowledge travels

Tacit knowledge resides in the minds of individual experts or in social groups and situations, and is often shared through conversations and interactions between people. Often deeply ingrained in experts' experience and intuition, it can be shared by fostering a collaborative and trust-filled environment, which involves creating opportunities for knowledge transfer through open communication, mentoring relationships, and team-building activities. The guide adds that encouraging face-to-face interactions and hosting regular brainstorming sessions helps make it more accessible.

The lessons learned register

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 repository. The register may include the category and description of the situation, and may also include the impacts, recommendations, and proposed actions associated with it. It records challenges, problems, realized risks and opportunities, or other content as appropriate.

When the register is created and who contributes

Here is the timing many get wrong: the register is created as an output of Manage Project Knowledge early in the project, then used as an input and updated as an output in many processes throughout. The persons or teams involved in the work are also involved in capturing the lessons learned — this is not the manager's task alone. Knowledge can be documented using videos, pictures, audio, or other suitable means that ensure the efficiency of the lessons captured. At the end of a project or phase, the information is transferred to an organizational process asset called a lessons learned repository.

On the Exam

The 2026 ECO gives knowledge transfer a task of its own in Domain I, People — the heaviest domain at 33%. Task 7, help ensure knowledge transfer, carries three stated enablers: identify knowledge critical to the project, gather knowledge, and foster an environment for knowledge transfer. The third is the most telling: what is asked for is creating an environment, not merely producing a document. In Domain III, Business Environment, Task 6, continuous improvement, connects through its enablers: utilize lessons learned; help ensure continuous improvement processes are updated; and update organizational process assets.

The dominant pattern is a scenario describing a departing expert or knowledge at risk of being lost, and asking what to do. Four keys settle most of it:

• An expert leaving whose knowledge is practical and intuitive → tacit; transfer through mentoring and direct interaction rather than requesting a report.
• A question about when lessons are documented → the register is created early and updated throughout.
• A question about who captures lessons → the persons or teams involved in the work.
• A question about where lessons go after closure → the lessons learned repository, an organizational process asset.

What deceives is options that look disciplined and documentary: asking the expert to write a detailed manual before leaving, deferring the lessons session to closure, or settling for archiving documents. All three address the explicit and leave the tacit, while the guide is explicit that tacit knowledge travels through conversations and interactions rather than codification alone. So does an option making lessons documentation the manager's sole responsibility.

Detailed Mistakes

Treating documentation as a synonym for knowledge transfer

The guide says outright that managing knowledge involves more than just documenting explicit knowledge for sharing or obtaining lessons learned at the end of the project. The reason is stated: codified knowledge lacks context and is open to different interpretations, so it is not always understood or applied in the right way. A document carries the answer and leaves behind the question it was born from; whoever reads it a year later learns what was done and not why the alternative was rejected.

Creating the lessons register late

The register is created early in the project as an output of Manage Project Knowledge, then used as an input and updated across many processes throughout. Deferring it to closure strips it of its first function — correcting course during execution — and turns it into an after-the-fact report written from a fading memory, by which point some of the people who lived the events have already left.

Confining documentation to written text

The guide notes that knowledge can be documented using videos, pictures, audio, or other suitable means that ensure the efficiency of the lessons captured. Much practical knowledge — the sequence of a procedure, a calibration method, the tone that works with a client — travels more clearly in two minutes of video than in two pages. Insisting on a single written template loses whatever resists written form, and puts the burden of translating knowledge into a language not its own on the person who holds it.

Where It Does Not Apply

Knowledge transfer presumes knowledge worth transferring and an environment that allows it. The guide requires a collaborative and trust-filled environment for sharing tacit knowledge, and where trust is absent no mandate helps: an expert who fears their knowledge is what makes them valuable will not hand it over however many templates you provide. A second, practical limit: identifying knowledge critical to the project is a separate ECO enabler preceding gathering it, so attempting to document everything produces a repository nobody searches. A third sits in the nature of tacit knowledge itself: it is challenging to transfer to others or to different projects, so knowledge bound to one project's context may not carry to another however well documented. The aim is not preserving everything, but preserving what will actually be reused — through the medium that suits its kind. One question settles what to keep: will a future project or an operational process need this, or is it a detail that ended when its context did?