Help ensure knowledge transfer
In the app: Project → Knowledge · Project → Closeout → Lessons learned
PMP ECO · People (33%) · Task P7. Make sure the knowledge the project depends on doesn't live in one person's head. Find it, name who holds it, and move it before it walks out the door.
What it is
Projects run on two kinds of knowledge:
- Explicit knowledge can be written down: drawings, specifications, procedures, data, the conditions on a permit. You transfer it by codifying it and filing it where people will find it.
- Tacit knowledge lives in people: experience, judgement, relationships, "why we did it this way". It is hard to write down, and a document usually loses the why. You transfer it by working together: shadowing, pairing, walk-throughs where the expert reasons out loud, joining the meetings where the knowledge is used.
Knowledge transfer means identifying the knowledge that is critical, knowing who holds it, and planning how it moves to someone else while the holder is still there. It runs through the whole project, not only at close. PMBOK® calls this managing project knowledge, and its running record is the lessons learned register.
Why it matters
- People rotate. On a two-and-a-half-year build, specialists leave, change roles or get pulled onto other projects. Their knowledge, and the risk mitigations built on it, leaves with them.
- A single holder is a single point of failure. Treat it like any other risk: give it an owner, a status and a response.
- The biggest losses happen mid-project, at hand-offs and demobilisations. By closeout the holder may already be gone.
- What you capture becomes an organisational process asset (OPA): the next project starts from your lessons instead of repeating your mistakes.
Where you do it in VanillaPM
- Knowledge (under Monitoring & Controlling in the project menu) is the critical-knowledge register. Each item records the topic, its kind (tacit or explicit), the holder, criticality, transfer status and the transfer plan. The tiles at the top count your single points of failure.
- Knowledge Base holds the explicit knowledge itself: the documents the transfer plans point to.
- Closeout → Lessons learned is the lessons learned register: what went well, what didn't, and recommendations. It sits under Closeout, but you can add lessons at any point, and you should.
Walked example — Coral Ridge Resort
Halfway through the build, the register holds six items. Four are high-criticality and not yet transferred. One is at risk: Tanvir, the MEP lead, is the only person who knows which salt-air coatings and details survived the mock-up, and he rotates to another project in January. That is tacit knowledge, so a spec sheet won't carry it. The plan has him pair with the facilities engineer on every plant-room inspection until he leaves. Meanwhile the ECA clearance conditions, which are explicit, are already transferred: the conditions register and monthly pack are in the Knowledge Base, and a second person has run the pack.
The workspace — the theory behind each screen
Every screenshot is the actual sample project, not a mock-up.
1 · Find the knowledge you can't afford to lose
The theory: critical knowledge and single points of failure. Not all knowledge needs a plan. Ask: if this person left tomorrow, what would we lose, and what would it cost? Rank the answers by criticality, then by how exposed they are right now.

Reading the screenshot: the tiles answer the question a sponsor actually asks. 4 single points of failure: high-criticality items not yet transferred. 1 at risk. 3 tacit, 3 explicit. 1 of 6 transferred. The list puts the most exposed item first: the MEP knowledge, high and at risk. Under each topic is how it transfers, so the register is a plan, not a list of worries. Notice the kinds: piling method, MEP detailing and the community relationships are tacit, so their plans involve people working alongside each other. The brand standards and the cost model are explicit, so their plans put documents in the Knowledge Base.
✅ Do rank by exposure: a high-criticality item held by someone about to leave goes first.
❌ Avoid registering everything. A register with fifty items is a register nobody reads.
2 · Match the transfer method to the kind of knowledge
The theory: tacit vs explicit transfer. Explicit knowledge transfers by codifying it. Tacit knowledge transfers by interaction: shadowing, pairing, storytelling, walk-throughs, communities of practice. Writing a document about tacit knowledge is the classic mistake. You get the what and lose the why.

Reading the screenshot: the MEP item is Tacit — in people, High, At Risk. The transfer plan names the trigger (Tanvir rotates in January) and the method (pairing on every plant-room inspection until then). The facilities engineer will live with these systems for decades, so that is the right person to learn from Tanvir. When the pairing is done, status moves to Transferred, and the tile count drops.
✅ Do start tacit transfers early. Pairing takes weeks, not a handover afternoon.
❌ Avoid "write it up before you go" as the only plan for tacit knowledge.
3 · Capture lessons while they're fresh
The theory: the lessons learned register. PMBOK® expects lessons to be recorded throughout the project and used on it, not only gathered at a closing workshop when memories have faded and half the team has left. At close, the register becomes an OPA for future projects.

Reading the screenshot: three lessons already, mid-build. What went well: sequencing piling around the monsoon saved about three weeks. What didn't: customs lead times on imports were underestimated. Recommendation: lock brand finishes at design stage. Each one is specific enough to act on, and the customs lesson can still change this project's remaining procurement.
✅ Do add a lesson at each milestone or retrospective, while the detail is fresh.
❌ Avoid "communication could be better". A lesson nobody can act on isn't a lesson.
Best practices & pitfalls
- Do treat a single knowledge holder as a risk, with an owner and a response.
- Do transfer during the project, especially before rotations and subcontractor demobilisation.
- Do build sharing into how the team already works: pairing on real tasks, a second person on recurring reports, joint stakeholder meetings.
- Pitfall: treating knowledge transfer as a closeout checkbox. By then the holder may be gone.
- Pitfall: a knowledge base full of documents nobody can find. Explicit knowledge only helps if it's filed where people look.
On the PMP exam
Know explicit vs tacit and which transfer method fits each. Expect scenarios where a key team member is leaving, or a new member keeps repeating a past mistake. The best answers build knowledge sharing into the way the team works (pairing, mentoring, an up-to-date lessons learned register used during the project) rather than a one-off document dump at the end. Remember that lessons learned are captured throughout the project and become OPAs at close.