Help Ensure Knowledge Transfer
The one-engineer problem: two kinds of knowledge
One engineer built the payment integration, understands every quirk of it, and is the only person who does. For months that is invisible and fine, right up until she gives notice, and the few weeks left on her calendar turn out to be the only window the project ever had to save what she knows. Most of it was never written down. That is the failure this task exists to prevent.
Projects run on two kinds of knowledge, and telling them apart is the whole foundation. Explicit knowledge is the documented kind: the plans, records, decisions, and procedures anyone can open and read. Tacit knowledge is the experience, judgment, and hard-won know-how that lives in a person's head and rarely reaches a page. Explicit knowledge is easy to store and easy to copy; tacit knowledge is the harder, more valuable half, and it is the easiest to lose, because when its holder walks out, it leaves with her. Losing the payment engineer costs the project her tacit knowledge, while the integration's config files, the explicit part, stay behind.
The PMP Examination Content Outline[1] frames the work as three responsibilities the project manager owns: identify the knowledge critical to the project, gather it, and foster an environment for knowledge transfer[1]. Read them, as the figure draws them, as one ongoing sequence rather than a checklist. You identify what is critical, you gather it while the context is fresh, and you foster the environment in which it moves from the people who hold it to the people who will need it. The rest of this page walks those three jobs, and because each one behaves differently for explicit and for tacit knowledge, the split between the two comes first.
Identify and gather before it walks out
Finding the critical knowledge is a deliberate step, not something you notice by accident. Start by asking which knowledge the project genuinely depends on, both the explicit records and the tacit expertise, and where each piece actually sits. The answer that matters most is a single point of failure: a task, system, or supplier relationship that only one or two people truly understand. The payment engineer from the last section was exactly this, and the time to spot her was months before her notice, not during it. Surface those concentrations early, while the holder is still on the team and there is still time to spread what they know.
Gather while the context is fresh
Once you know what is critical, gather it continuously rather than saving it all for a closeout meeting. Gathering knowledge[1] throughout the project keeps lessons accurate, because detail fades fast, and it lets the current project act on what it learns instead of handing every insight to some future team. A lessons-learned session held only at closure captures a blurred version of events and helps no one still working the project. The figure contrasts the two: lessons captured in each phase or iteration flow into one shared repository as the work runs, where a single end-of-project session would try to reconstruct them all at once.
On adaptive work, the retrospective is the engine
Adaptive delivery (iterative, agile work planned in short increments) builds this habit into its cadence through the retrospective, a recurring session where the team inspects how it worked and decides what to change. The Agile Manifesto states the underlying rule directly: at regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly[2]. Scrum names this the Sprint Retrospective[3] and is explicit that the most impactful improvements are addressed as soon as possible, and may be added to the next Sprint's work[3]. The trap is to run the retrospective as a venting ritual: a session that surfaces problems but changes nothing next iteration has collected a complaint, not a lesson.
Foster the environment: how tacit knowledge moves
Gathering knowledge is wasted effort if the environment does not let it move, and moving tacit knowledge is a different problem from moving explicit knowledge. Explicit knowledge transfers by being stored somewhere readable; tacit knowledge does not survive that trip. The Agile Manifesto puts the mechanism plainly: the most efficient and effective method of conveying information to and within a team is face-to-face conversation[2]. In practice, pairing (two people doing the work together), shadowing (one person watching another do the work), and mentoring transfer judgment far better than a handover document can, because the receiver gets to ask the questions a document never anticipated.
People share only when it is safe to
None of that interaction happens on command. People share hard-won knowledge when they feel safe and when they see collaboration valued and rewarded, not when they are handed a documentation quota. The Agile Manifesto's advice is to build projects around motivated individuals, give them the environment and support they need, and trust them[2], and fostering that culture is the project manager's real lever here. A blanket order to document everything produces box-ticking compliance, while the judgment you most wanted to preserve stays locked in people's heads.
Plan the handover at every transition
Team changes are the moment knowledge is most at risk, so plan for them rather than reacting to them. When a member joins, deliberate onboarding brings them up to the team's shared understanding; when a member leaves, a structured handover with an overlap period lets the successor absorb the tacit know-how by working alongside them, as the figure shows, while the explicit parts are written into the shared store. Letting a departing member walk out with no structured handover forfeits exactly the critical knowledge you identified earlier.
Store it where the team will look
The explicit half of the job ends in a repository, and the test of a good one is simple: can a teammate who needs the knowledge actually find it? Knowledge captured into personal notes, private drives, and email threads is effectively lost even though it was written down, because no one else can locate it. Store gathered knowledge in a shared, findable place the team already uses, so that reuse is the path of least resistance rather than an archaeology project.
Reading the exam: stems, right answers, and traps
PMP items on this topic are situational, and they reward one consistent instinct: preserve and move the knowledge, especially the tacit knowledge, before it is gone. Recognizing the pattern in the stem is most of the work.
- One person is the only one who knows. When a stem describes a task, system, or vendor relationship that a single team member understands, the credited answer spreads that knowledge now, through pairing, shadowing, or documentation. The trap waits until the person is already leaving, or accepts the single-point risk with no action.
- A key member is about to leave. The credited answer plans a structured handover with an overlap so the successor learns by working alongside them. Trap answers rely on a document written on the last day, or reassign the work and hope.
- Lessons only at the end. When the stem offers to defer all lessons capture to project closure, that is a wrong answer dressed as diligence; the credited move gathers lessons throughout so this project benefits, not only the next one.
- A retrospective that changes nothing. When an adaptive team keeps hitting the same issue, the answer is to act on the retrospective's findings in the next iteration, not to hold more meetings or escalate. Treating the retrospective as a status update is the planted distractor.
- Mandate versus culture. When people are not sharing, the credited answer builds the safety and incentives that make sharing worthwhile; ordering everyone to document more is the tempting wrong choice, because it treats the symptom and not the willingness.
- Scattered but written down. When knowledge exists only in personal notes or inboxes, the credited answer consolidates it into the shared, findable repository. Assuming it is safe because someone wrote it down somewhere is the trap.
Across all of them the throughline matches the People domain's focus on leading and enabling the team[4]: the project manager identifies the critical knowledge, gathers it while the context is fresh, and fosters the environment that moves it, reaching for documentation as one tool among several rather than the whole answer. When two options both look reasonable, prefer the one that transfers tacit knowledge through people over the one that only files another document.
The knowledge-transfer job for explicit vs tacit knowledge
| Project manager's job | Explicit knowledge | Tacit knowledge |
|---|---|---|
| Identify what is critical | Catalog the key documents, records, and decisions the project depends on | Find who holds the experience and judgment that others quietly depend on |
| Gather it | Capture and file it continuously while the context is fresh | Draw it out through conversation, retrospectives, pairing, and shadowing |
| Foster its transfer | Store it in a shared, findable repository people can read | Transfer it person-to-person through pairing, shadowing, and mentoring |
| Main loss risk | Goes stale, or scatters into personal notes and inboxes | Walks out the door when the person leaves; the easiest knowledge to lose |
Decision tree
Sharp facts the exam loves — give these one last read before exam day.
Cheat sheet
Sharp facts the exam loves — scan these before test day.
- Identify the knowledge critical to the project, both explicit and tacit
Ensuring knowledge transfer starts by identifying the knowledge critical to the project, both explicit knowledge that is documented and tacit knowledge held as personal experience and judgment. Tacit knowledge is the easiest to lose.
Trap Assuming only documented, explicit knowledge matters and overlooking the tacit know-how in people's heads.
14 questions test this
- During planning for a multi-year public-sector modernization project, the project manager learns that a long-tenured business analyst is the sole source of knowledge about the legacy processes the new
- A predictive project is approaching closure, and the delivery team will be reassigned to other work within a month. The operations group that will run the product afterward has already received the us
- A predictive clinical-systems validation project depends on one compliance specialist who is the only person able to interpret how the applicable regulatory requirements apply to the project's deliver
- A project manager is launching a hybrid consumer-electronics initiative that has no comparable predecessor to draw on, and the sponsor wants assurance that hard-won expertise will not be lost as speci
- While facilitating a risk-identification session on an agile fintech product, the project manager realizes that only one engineer understands how the team decides when a release is safe to promote and
- While planning knowledge management for a large cross-functional program, the project manager wants to find out, before any problem arises, where the program's most critical expertise is concentrated
- A project manager launching a complex integration effort finds the team eager to begin knowledge transfer, but they disagree on scope: some want to document every process the team touches, while other
- A newly chartered infrastructure project inherits a mature library of runbooks, design documents, and archived meeting minutes from a similar past effort, and the sponsor assumes that knowledge transf
- Midway through an agile software-as-a-service program, an internal knowledge-management review reports that every process the team follows is now fully documented and concludes that the program faces
- A hybrid project must satisfy new environmental-sustainability reporting obligations, and only one specialist on the team fully understands how those evolving regulatory requirements translate into th
- Under schedule pressure, a program sponsor tells the project manager to drop the planned knowledge-capture activities so the team can focus entirely on delivery. The project manager is concerned that
- A project manager is setting up knowledge transfer for a data-platform project and is evaluating an AI assistant that can automatically scan and summarize the team's documents, tickets, and chat histo
- On an agile product team, the working agreements, coding conventions, and most architecture decisions are already recorded in the team wiki. What is not written down anywhere is how the lead developer
- On an adaptive analytics project, most of the pipeline is well documented, but the way one data scientist decides how to tune and validate the models rests on experience and intuition that has never b
- Spot key-person knowledge concentrations early
The project manager identifies where critical knowledge is concentrated in one or two people, so it can be shared before a departure creates a gap. Waiting until someone leaves to notice the dependency is too late.
Trap Addressing single-point knowledge dependencies only after the key person has already left.
11 questions test this
- During planning for a multi-year public-sector modernization project, the project manager learns that a long-tenured business analyst is the sole source of knowledge about the legacy processes the new
- A predictive project is approaching closure, and the delivery team will be reassigned to other work within a month. The operations group that will run the product afterward has already received the us
- A predictive clinical-systems validation project depends on one compliance specialist who is the only person able to interpret how the applicable regulatory requirements apply to the project's deliver
- While facilitating a risk-identification session on an agile fintech product, the project manager realizes that only one engineer understands how the team decides when a release is safe to promote and
- Midway through a predictive engineering project, the project manager realizes that a single senior systems engineer is the only person who understands how several interdependent legacy components fit
- While planning knowledge management for a large cross-functional program, the project manager wants to find out, before any problem arises, where the program's most critical expertise is concentrated
- A project manager launching a complex integration effort finds the team eager to begin knowledge transfer, but they disagree on scope: some want to document every process the team touches, while other
- Midway through an agile software-as-a-service program, an internal knowledge-management review reports that every process the team follows is now fully documented and concludes that the program faces
- A hybrid project must satisfy new environmental-sustainability reporting obligations, and only one specialist on the team fully understands how those evolving regulatory requirements translate into th
- A business analyst who is the only person deeply familiar with the client's legacy approval rules has just given two weeks' notice, and several upcoming deliverables depend on that understanding. None
- On an adaptive analytics project, most of the pipeline is well documented, but the way one data scientist decides how to tune and validate the models rests on experience and intuition that has never b
- Gather knowledge and lessons continuously, not only at closure
Knowledge and lessons learned are captured throughout the project, while the context is fresh, rather than reconstructed at closure. Continuous capture lets the current project benefit, not just future ones.
Trap Deferring all lessons-learned capture to a single session at the end of the project or phase.
12 questions test this
- An adaptive team holds a retrospective at the end of every two-week iteration. For four iterations running, the team has raised the same complaint, an unstable test environment that repeatedly stalls
- An adaptive team holds a retrospective at the end of every two-week iteration. For four iterations running, the team has raised the same complaint, an unstable test environment that repeatedly stalls
- A newly formed adaptive team is delivering in two-week iterations but has decided to hold only one retrospective, at the end of the entire release, on the reasoning that by then it will have the fulle
- Early in a lengthy predictive construction-technology project, the team develops an unusually effective way of coordinating field inspections that removes a bottleneck which had been slowing the first
- A specialized data-migration engineer, contracted for a single workstream of a multi-phase predictive program, has completed that workstream and rolls off the project next week, even though several la
- A major deliverable of a multi-phase program has been completed and is about to be handed to the organization's operations and support group for day-to-day running, while the program itself continues
- On an ongoing project, a fixed-scope vendor engagement for one subsystem has just been completed and formally closed out, while three more procurements of a very similar nature are still planned for l
- A new team member joins a predictive project several months into execution and, hoping to avoid repeating mistakes, asks the project manager how the team keeps track of what it has already learned the
- Taking over a predictive project that is already in execution, a project manager reviews the plan and finds that lessons-learned activity is scheduled as a single workshop during project closure. The
- An organization diligently documents lessons learned into a central repository at every project's closeout, yet the same avoidable mistakes keep recurring project after project. Newly assigned to anot
- During an adaptive team's iteration retrospective, the members agree that swarming on one high-priority item at a time, rather than starting many items in parallel, would meaningfully cut the team's c
- A hybrid project is delivering a corporate sustainability initiative, and partway through, the team discovers a far better way to gather supplier emissions data, one that would cut rework on several d
- Adaptive teams use retrospectives to capture and immediately apply lessons
On adaptive work the team runs regular retrospectives to inspect how it is working and to capture lessons it then acts on in the next iteration. A retrospective that never changes behavior wastes the learning.
Trap Holding retrospectives as a ritual but never converting the findings into concrete improvements.
8 questions test this
- An adaptive team holds a retrospective at the end of every two-week iteration. For four iterations running, the team has raised the same complaint, an unstable test environment that repeatedly stalls
- An adaptive team holds a retrospective at the end of every two-week iteration. For four iterations running, the team has raised the same complaint, an unstable test environment that repeatedly stalls
- A newly formed adaptive team is delivering in two-week iterations but has decided to hold only one retrospective, at the end of the entire release, on the reasoning that by then it will have the fulle
- During an iteration retrospective, an adaptive team runs an AI assistant that analyzes its workflow metrics and reports that code review is the team's single largest source of delay. Some members want
- Two iterations ago, an adaptive team agreed in its retrospective to add a new verification step to its definition of done in order to reduce the defects that were escaping to testing, and the change w
- On an adaptive team, the iteration retrospective has gradually drifted into a status update in which members report task progress and occasionally blame one another, and unsurprisingly the team's way
- An adaptive team has run a retrospective at the end of every iteration for months and dutifully produces a list of improvement ideas each time. Yet stakeholders observe that the team's throughput and
- During an adaptive team's iteration retrospective, the members agree that swarming on one high-priority item at a time, rather than starting many items in parallel, would meaningfully cut the team's c
- Foster a safe, collaborative environment where people share knowledge
Knowledge transfer depends on culture: people share freely when they feel safe and see collaboration valued and rewarded. The project manager fosters that environment, since mandating documentation alone does not create willingness to share.
Trap Ordering people to document everything without building the trust and incentives that make them want to share.
9 questions test this
- Frustrated that valuable know-how leaves with departing staff, an executive directs the project manager to enforce a rule that every team member document all their work in a central repository. Weeks
- On a program where several teams solve similar problems in isolation, the project manager notices engineers rarely share reusable solutions, and those who do receive no acknowledgment while being meas
- Adoption of the project's knowledge-sharing practices has stalled; team members treat sharing as an imposition and quietly opt out. A colleague suggests deploying an AI assistant to automatically capt
- Over the last few retrospectives, after a junior member's improvement suggestion was openly ridiculed by a senior colleague, the team has gone quiet and stopped raising ideas or surfacing problems. Th
- A fully remote team spread across several time zones completes its work almost entirely through tickets and formal documents, and members rarely interact beyond what a task strictly requires. As a res
- A PMO sponsor asks the project manager to help launch a community of practice so specialists scattered across several projects can exchange lessons and solve recurring problems together. An earlier at
- A project team has just been assembled from two internal departments that previously competed for budget and recognition, and the two groups distrust each other. Members guard their expertise and rare
- A newly formed delivery team has repeatedly hidden defects and rework until they became costly, and in interviews members admit they avoid raising problems because earlier disclosures were met with bl
- The project manager wants knowledge sharing to become a lasting part of how the team works, not a one-off campaign. A team lead proposes setting a mandatory quota that requires each member to post a f
- Tacit knowledge transfers through interaction more than documents
Tacit knowledge moves person-to-person through interaction such as pairing, shadowing, and mentoring, far more effectively than through documents alone. The project manager creates occasions for that direct exchange.
Trap Relying only on written handover documents to transfer experience-based, tacit knowledge.
11 questions test this
- A complex new feature requires blending the specialized know-how of several team members from different disciplines. So far the team has coordinated by passing design documents back and forth for revi
- Frustrated that valuable know-how leaves with departing staff, an executive directs the project manager to enforce a rule that every team member document all their work in a central repository. Weeks
- Two project teams in different regions have each solved a similar, tricky integration problem in their own way. The project manager wants the hard-won, experience-based lessons to flow both directions
- A lead systems architect who holds deep, undocumented experience with the project's legacy integrations is leaving in six weeks. The project will continue for another year, and several less-experience
- A project phase has just finished, and the team learned hard lessons about integrating a difficult third-party payment gateway. A similar phase begins next month with several new members who were not
- Several new engineers have joined a fast-moving agile team midway through delivery. They have read the project's written documentation but still struggle to apply the team's practical techniques and m
- A fully remote team spread across several time zones completes its work almost entirely through tickets and formal documents, and members rarely interact beyond what a task strictly requires. As a res
- A junior project team member can follow the documented process steps but consistently misjudges when to escalate emerging risks and how to read stakeholder concerns, the kind of judgment the team's ve
- A software project is approaching transition to the operations group that will support the system after go-live. A detailed support manual has been written, but the delivery team has accumulated exper
- On a multiyear product, only one senior engineer can reliably diagnose failures in the core billing service. She is staying with the team, but the project manager worries that delivery would stall if
- An agile team keeps releasing similar defects because only two experienced members apply a nuanced code-review technique that the rest of the team has not absorbed. The technique is already written up
- Plan knowledge transfer at team transitions and onboarding
When members join or leave, the project manager plans deliberate handover and onboarding so continuity survives the personnel change. Letting a departing member walk out without a handover forfeits critical knowledge.
Trap Allowing a departing team member to leave with no structured handover of what they know.
18 questions test this
- On a year-long hybrid initiative, the project manager realizes that several critical components each depend on a single specialist who alone understands them, even though no one has announced any plan
- A specialist who owns a complex, sparsely documented component on a hybrid project will transfer to another program in three weeks, and their named successor is already on the team. Management has app
- A project's only database expert has accepted a role on another program and will transfer out in three weeks. A well-maintained technical wiki documents the database's configuration, but much of what
- Two weeks from now, the project manager of a large predictive construction project will be reassigned to a higher-priority program, and a successor has already been named. Extensive plans, registers,
- A team member who owns several in-progress deliverables has just been promoted and will move to another project at the end of the sprint. A successor has been named but is new to this project's work.
- A newly hired project lead is joining a strategic transformation program several months into delivery, replacing a lead who left. The onboarding materials are heavy on task lists, schedules, and tool
- To meet rising demand, an agile product team is doubling in size over the next two sprints, with several new developers joining at once. The existing members worry that stopping to explain the evolved
- As a project moves from build into a lighter support phase, four of the eight team members will be released over the next month to staff other initiatives, while a smaller core team continues. Several
- On an agile project, the Scrum Master who has coached the team for a year is rotating to another team next sprint, and a colleague new to this team will take over the facilitation role. The team's wor
- On a long-running hybrid program with frequent team rotation, the project manager notices that useful decisions, workarounds, and stakeholder agreements are being lost each time someone rolls off, bec
- During procurement planning for a predictive project, the project manager decides to outsource a specialized subsystem to an external vendor. Once the engagement ends, the organization's own staff wil
- A senior developer who was building a partially finished, undocumented module on a hybrid project has resigned effective immediately for personal reasons, with no handover completed. The module sits o
- During planning of a predictive project, the project manager knows that a specialist contractor engaged only for the design phase will roll off at the phase gate, after which an internal team will car
- Midway through an agile delivery, a new developer joins a cross-functional team that is already several sprints into the work. The product backlog, team norms, and domain context have evolved consider
- A predictive program is organized into five sequential phases spanning two years, and a largely different team will staff each phase. The project manager wants the rationale behind each phase's design
- A predictive project is nearing closure, and the delivered system will be handed to an operations team for ongoing support. The project team is scheduled to disband within days of go-live, and the ope
- A senior integration specialist who is the only person who understands a project's legacy interface has given two weeks' notice. This work is on the critical path and will continue for several more mo
- A departing team lead suggests that, instead of holding handover meetings, the team simply feed all their chat logs and documents into a generative-AI assistant that will summarize everything for the
Captured knowledge only delivers value if it is stored where the team can readily find and reuse it. Knowledge scattered across personal notes and inboxes is effectively lost even though it was written down.
Trap Capturing knowledge in scattered personal notes that no one else can locate or access.