Knowledge transfer and lessons learned are the two topics candidates most often file under "closing the project" and then never think about again. On the current exam that filing is wrong twice over. Neither topic lives in closure, and they do not live in the same domain as each other.
PMI's Project Management Professional (PMP) Examination Content Outline dated July 2026 places "Help ensure knowledge transfer" in the People domain, and puts lessons learned inside a Business Environment task called "Continuous improvement." If you studied from materials built on the previous outline, both were somewhere else.
Where these topics sit now
The 2026 outline splits the exam into People 33%, Process 41%, and Business Environment 26%. Independent summaries of the change published by PMP trainers put the previous weighting at People 42%, Process 50%, and Business Environment 8% — which is why so much reorganization lands in that third domain.
| Topic | Previous outline | 2026 outline |
|---|---|---|
| Knowledge transfer | A Process task | People, Task 7 |
| Managing communications | A Process task | People, Task 8 |
| Lessons learned, improvement, process asset updates | Scattered enablers | Business Environment, Task 6 |
| Final lessons learned and retrospectives | Closing activity | Process, Task 10, as a closeout activity |
Note the last two rows. Lessons learned appears in two places, and the exam treats them differently. One is something you do continuously. The other is something you conclude at the end of a project or phase.
What the outline actually asks for
The People task is short enough to quote in full. "Help ensure knowledge transfer" carries three enablers:
- Identify knowledge critical to the project
- Gather knowledge
- Foster an environment for knowledge transfer
Read those as a sequence and notice what is absent. There is no enabler about writing a document. The first step is deciding which knowledge matters, which means knowledge transfer is a risk-reduction activity before it is a documentation activity. The knowledge that matters is the knowledge whose loss would hurt — a single person who understands the legacy integration, an undocumented vendor workaround, a design decision nobody wrote down.
The third enabler is the one that explains why this became a People task. "Foster an environment" is behavioural. The exam is asking whether you can create conditions where people share what they know, not whether you can mandate a template.
Lessons learned is an improvement task, not a closeout ritual
Business Environment Task 6, "Continuous improvement," has three enablers:
- Utilize lessons learned
- Help ensure continuous improvement processes are updated
- Update organizational process assets (OPAs)
The verb in the first enabler is "utilize," not "capture." That wording is the whole point. A question that describes a team recording a lesson has not yet reached the behaviour the outline rewards. The behaviour it rewards is using a lesson — from this project or a previous one — to change how the work is done.
The third enabler closes the loop outward. Organizational process assets are the organization's own templates, procedures, and historical records. Updating them is how a lesson stops being private to one team. If an answer option captures a lesson but leaves the organization's process assets untouched, it has done half the job.
How questions use the distinction
Four scenarios, four different correct behaviours. The wording of the stem is what separates them.
A key developer is leaving in three weeks and is the only person who understands a critical component. This is knowledge transfer, People Task 7. The first move is identifying what knowledge is actually critical and arranging transfer — pairing, walkthroughs, documented handover — not filing a lessons learned entry. The departure is the trigger; the risk is concentration of knowledge in one person.
Mid-project, the team identifies a recurring cause of rework and the same problem happened on the previous project. This is continuous improvement. A lesson already exists and is not being used. The answer applies it now and updates the relevant process asset, rather than noting it for the final report.
The team runs a retrospective at the end of an iteration and agrees on two changes. This is improvement in its adaptive form. Retrospectives are named in the outline as a closeout activity, but an iteration retrospective mid-project is the continuous improvement task in practice. What makes an answer correct is whether the agreed changes are implemented and tracked, not whether the retrospective was held.
The project is complete and the sponsor has accepted the deliverables. Now you are in Process Task 10. The outline's closure enablers name "final lessons learned, retrospectives, procurement, financials, resources" together. Final lessons learned belongs here, alongside transition readiness and approval.
Retrospectives and lessons learned are not synonyms
Candidates often use the two words interchangeably, and the exam does not. A retrospective is an event — a facilitated session, usually at the end of an iteration, that produces agreed actions for the next one. Lessons learned is a body of recorded knowledge that accumulates across a project and feeds the organization afterward.
The practical difference on the exam is cadence and audience. A retrospective is for the team, soon. Lessons learned is for the organization, later. A question that describes an immediate team-level change points at the retrospective. A question that describes something the next project should know points at lessons learned and the process assets.
Because roughly 40% of items reflect predictive approaches and the remaining 60% split between adaptive and hybrid, according to the 2026 outline, you should expect this topic in both vocabularies. The same underlying behaviour appears as a retrospective in one stem and a lessons learned review in another.
Traps worth recognizing
"Document it in the lessons learned register" offered for a live problem. Recording is not resolving. If the scenario describes something currently blocking the team, the answer acts first.
Waiting until closure. Any option that defers capture or improvement to the end of the project is usually wrong. Both outline tasks are continuous.
Treating knowledge transfer as a Process activity. It moved. Scenarios about handover, onboarding, departures, and single points of failure are People items, and the answer usually involves people doing something together rather than a document being produced.
Stopping at the team boundary. A lesson that improves one team but never reaches the organization's process assets misses the third enabler of the Business Environment task.
Confusing a lesson with a change request. A lesson changes how work is done next time. If the scenario requires altering approved scope, schedule, or cost now, that is change control, not improvement.
What to study
Read the three enablers of People Task 7 and the three of Business Environment Task 6 side by side until the split is automatic: critical knowledge and the conditions for sharing it on one side, using lessons and updating process assets on the other. Then work through mock questions sorting them by which of the two tasks is being tested, rather than by right and wrong.
The reorganization matters more than it looks. Business Environment grew to roughly a quarter of the exam, and continuous improvement is one of the tasks that filled it. A study plan that still treats lessons learned as a paragraph in the closure chapter is underweighting a topic the current outline gives its own task.