about 4.1% of the exam content - about 90 minutes - 14 practice questions
0:00 / --:--
Reading
GCHS has a superintendent who knows which Galveston County inspectors want the blocking photographed before
drywall, which supplier actually stocks ADA-compliant lever hardware, and how to talk to an anxious homeowner on
demolition day. None of that is written down anywhere. If he retires, or takes a job with a builder, the
organization pays to relearn it, one mistake at a time. Knowledge transfer is the deliberate work
of making sure what people know outlives their assignment to the project.
Explicit knowledge moves through documents and training material; tacit knowledge moves through
people, via pairing, shadowing, mentoring, and communities of practice. Both feed the project's lessons
learned register, which transfers to the organization's lessons learned repository at close-out.
Two kinds of knowledge
PMI splits knowledge into two types, and the split drives the technique you choose.
Explicit knowledge
Tacit knowledge
What it is
Facts, procedures, data that can be written down
Experience, judgment, intuition, know-how
GCHS example
The grab bar installation spec; the permit checklist
Knowing a floor joist is compromised from how it sounds underfoot
Transfer method
Documents, templates, databases, training material
Pairing, shadowing, mentoring, storytelling, communities of practice
Main risk
Codified but never used or found
Never captured; leaves with the person
The classic mistake is trying to solve a tacit problem with an explicit tool. Writing a longer manual will not
transfer a superintendent's judgment. Putting a junior lead beside him for six weeks will.
Lessons learned: register versus repository
These are two different artifacts and the exam expects you to know which is which.
Lessons learned register
Lessons learned repository
A project document, created early and updated throughout
An organizational asset spanning many projects
Owned by the project; used by the current team
Owned by the organization or PMO; used by future teams
Captures situation, impact, recommendation as it happens
Receives the register's content at phase end and close-out
Improves this project while it is still running
Improves the next project
Two implications matter. First, lessons are captured continuously, not in a single meeting at the end
when everyone has forgotten the details and moved on. Second, a lesson that never reaches the repository, or reaches
it and is never searched, has produced no organizational value at all.
Key points
Explicit knowledge transfers through documents; tacit knowledge transfers through people
The lessons learned register is a project document; the repository is an organizational asset
Capture lessons throughout, not only at close-out
Retrospectives improve the team's process; lessons learned inform future projects, related but not identical
Knowledge that is captured but never retrieved has produced no value
Techniques that actually move knowledge
Pairing: two people doing the work together, deciding together. The highest-bandwidth
transfer there is, and the reason agile teams use it.
Shadowing and reverse shadowing: the learner watches, then does the work while the expert
watches. Reverse shadowing is where the real gaps surface.
Mentoring: a longer relationship focused on judgment and career growth rather than a
specific task.
Communities of practice: people with a shared craft who meet across project boundaries, such as all
GCHS site leads comparing notes monthly on accessibility retrofits. Voluntary, cross-cutting, and the main way
tacit knowledge spreads horizontally in an organization.
Retrospectives: held every iteration in adaptive work, focused on how the team works and on
committing to a few concrete improvements. A retrospective with no action item is a venting session.
Storytelling and work shadowing on site: narrative sticks where bullet points do not,
especially for judgment calls and near-misses.
Onboarding and handover protocols: a defined transition when someone leaves the project,
not a farewell email.
Transfer at transitions and at close-out
The riskiest moments for knowledge loss are transitions: a crew lead reassigned mid-project, a phase gate, a
contractor's demobilization, or final handover of a rehabbed home to the homeowner. Handover to the operating owner
is knowledge transfer too; the homeowner needs to know how the new HVAC filter is changed, what the warranty covers
and for how long, and who to call. A project is not done when the work is done; it is done when the person who lives
with the result knows how to live with it.
At close-out, the deliverables are the final lessons learned transfer to the repository, updated organizational
process assets, and archived project records. Knowledge transfer is one of the specific reasons close-out exists; skipping it saves a week and costs the next project a month.
The end-of-project lessons meeting is too late
By close-out, the team has dispersed, memories have blurred, and no one can act on what is learned. Capture the
lesson within days of the event, in the register, with enough context that a stranger could use it, and hold
retrospectives on a cadence so improvements land while the project can still benefit.
Where AI helps, and where it does not
AI tools are genuinely useful for the explicit side: summarizing meeting notes into draft lessons, tagging and
making a repository searchable so people actually find the entry about hurricane-season material lead times, and
surfacing similar past projects during planning. That last capability is the real prize: a searchable repository
with good retrieval turns dead archives into a working asset.
What AI does not do is transfer judgment. It cannot put a new site lead's hands on a compromised joist, and it
cannot give a homeowner confidence in the person standing in her kitchen. Treat AI output as a draft that a
knowledgeable human reviews for accuracy before it becomes an organizational record.
Practice Questions
1. A GCHS superintendent with 20 years of judgment about coastal framing is retiring in three months. What is the BEST knowledge transfer approach?
Add his phone number to the emergency contact list
Record a series of interview videos for the archive
Pair a junior site lead with him on active jobs, from shadowing to reverse shadowing
Ask him to write a comprehensive procedures manual covering every framing detail before he retires
Answer: c. Judgment is tacit knowledge and transfers person-to-person through doing the work together, not through documents. A manual and videos can capture explicit facts but cannot convey how he reads a compromised joist.
2. Which BEST distinguishes the lessons learned register from the lessons learned repository?
The register is kept in electronic form for the team, while the repository is a paper archive for the organization
The register is for failures; the repository is for successes
The register is a project document; the repository is an organizational asset for future projects
They are the same artifact under two names
Answer: c. The register belongs to the current project and improves it while it runs; content flows to the repository at phase ends and close-out for future teams. Both capture successes and failures alike.
3. When should lessons learned be captured on a project?
Continuously, as events occur throughout the project
At the midpoint review
When the sponsor requests them
Only at project close-out
Answer: a. Continuous capture preserves detail while it is fresh and lets the current project benefit from its own learning. Waiting for close-out produces vague entries no one can act on.
4. Which is an example of explicit knowledge?
Sensing that a subcontractor is about to fall behind
Knowing how to calm an anxious homeowner on demolition day
Judging whether a slab crack is structural
The documented grab bar mounting specification
Answer: d. Explicit knowledge can be written down and transferred through documents. The other three are experience-based judgment that resists codification.
5. A retrospective ends with a good discussion but no commitments. What should the project manager or facilitator do?
Accept it as a healthy venting session, since open discussion is the main value of the event
Cancel future retrospectives
Escalate the lack of engagement to management
Guide the team to pick concrete improvement actions with owners for the next iteration
Answer: d. A retrospective produces committed improvements; without action items nothing changes and the team learns the ceremony is theater. Escalating or cancelling abandons the improvement mechanism entirely.
6. What is a community of practice?
A subset of the change control board
A mandatory project team meeting held weekly to review status, issues, and upcoming work packages
A regulatory body that certifies practitioners
A voluntary cross-project group with a common craft that exchanges knowledge and practices
Answer: d. Communities of practice are voluntary and cut across project boundaries, which is how tacit knowledge spreads horizontally in an organization. They are not project meetings and have no governance authority.
7. A site lead is being reassigned to a new project effective next week, and has unique judgment about coastal framing failures. What should the project manager do FIRST to protect that knowledge before the transition?
Send a farewell email summarizing his contributions
Ask him to write down everything he knows before he leaves
Begin a structured handover, pairing him with his successor for the remaining days
Wait until the transition to see what knowledge gaps appear
Answer: c. Pairing transfers tacit judgment while time still remains, which a farewell note cannot do. A written summary captures only the explicit portion, and waiting risks losing the knowledge entirely once he leaves.
8. A junior estimator has shadowed a senior estimator for two weeks. What should happen NEXT to confirm the transfer of judgment is actually working?
The junior estimator performs the task while the senior observes and corrects (reverse shadowing)
The senior estimator writes a detailed procedures manual covering every estimating step and hands it over
The junior estimator takes over unsupervised immediately
The pairing ends because two weeks is the standard duration
Answer: a. Reverse shadowing surfaces whether the learner can actually apply the judgment, which passive shadowing alone cannot confirm. A manual addresses explicit facts, and removing supervision or ending on a fixed clock ignores whether the transfer actually took.
9. What is the main organizational benefit of a community of practice, compared to a single project team's internal meetings?
It spreads tacit knowledge horizontally across projects, among people who share a craft
It replaces the need for a lessons learned repository
Participation is mandatory for certification renewal
It has formal decision-making authority over the scope, budget, and staffing of active projects
Answer: a. Cross-project, voluntary knowledge sharing among practitioners is exactly what distinguishes a community of practice from a project team meeting. It carries no governance authority and does not substitute for the repository.
10. How does mentoring differ from pairing as a knowledge transfer technique?
The two terms describe the same technique
Mentoring is a longer relationship focused on judgment and growth; pairing is task-focused work done together
Mentoring applies only to executives
Pairing requires no direct interaction between the two people, who each work alone on separate tasks and share results by email later
Answer: b. Mentoring runs over a longer span and targets judgment and growth, while pairing is immediate, task-bound, shared work. Neither is restricted to executives, and they are distinct techniques with different bandwidth and duration.
11. A team's retrospectives keep surfacing the same recurring problem without anything actually changing. What is the MOST likely cause?
The team lacks the authority to make any changes at all
Retrospectives are not producing committed, owned improvement actions
The problem is inherently unsolvable
The facilitator is not a certified scrum master
Answer: b. A retrospective without concrete, owned action items is a venting session, and the same issue naturally recurs. Facilitator certification is not the mechanism at fault, and assuming the problem is unsolvable skips the more likely explanation.
12. Which is the MOST appropriate use of AI in knowledge management?
Automatically publishing AI-drafted lessons learned to the repository with no review, so future teams get them as fast as possible
Using AI to tag and search lessons learned entries, with a knowledgeable person reviewing drafts before they become records
Replacing shadowing and mentoring with AI-generated training videos
Letting AI make final scope decisions based on patterns in past project data
Answer: b. AI is genuinely useful for the explicit, searchable side of knowledge management, with human review before anything becomes an organizational record. It cannot transfer judgment, and unreviewed publishing or AI-made scope decisions remove necessary accountability.
13. A rehab project reaches substantial completion. What must still happen before the project is truly closed, beyond finishing the physical work?
The homeowner must be walked through operating and maintaining the new systems and warranty
The final invoice must be paid
Nothing further; the work itself is done
The crew must be reassigned immediately to the next job so that labor costs stay under the budget
Answer: a. Handover to the person who lives with the result is knowledge transfer too, and the project is not done until she knows how to live with it. Reassigning the crew or paying the invoice may happen, but neither substitutes for that handover.
14. A team captures a lesson about hurricane-season material lead times in its lessons learned register during the project. For that lesson to actually benefit future GCHS projects, what must also happen?
It must be shared verbally at an all-staff meeting
It must be transferred to the organizational lessons learned repository for future teams
Nothing; the register alone is sufficient
It must be approved by the change control board before it can be added to any project document
Answer: b. A register serves only the current project; the lesson creates organizational value only once it reaches the searchable repository that future teams actually use. A verbal mention or the register alone leaves it undiscoverable once the project disperses.
Glossary
Explicit knowledge
Facts, procedures, and data that can be written down and transferred through documents, templates, and training material.
Tacit knowledge
Experience, judgment, and intuition that resist codification and transfer primarily through people.
Lessons learned register
A project document, created early and updated continuously, capturing situation, impact, and recommendation as events occur.
Lessons learned repository
An organizational asset spanning many projects, populated from registers at phase ends and close-out, for future teams to search.
Pairing
Two people performing the work together and deciding together; the highest-bandwidth tacit knowledge transfer technique.
Shadowing / reverse shadowing
The learner first observes an expert performing the work, then performs it while the expert observes and corrects.
Mentoring
A longer-term relationship focused on developing judgment and career growth rather than a single task.
Community of practice
A voluntary, cross-project group of people sharing a common craft who exchange knowledge and practices.