September 7, 2026 · 7 min read
TL;DR: Lessons learned appears 48 times as an answer option across this bank and is keyed 12 times. The single most common reason a lessons-learned option fails is that it waits: until the end of the project, until after the release, until the post-mortem. Lessons are recorded as they are identified, and the current project is supposed to benefit from them.
Almost every candidate knows lessons learned are important. Almost every candidate has also worked somewhere that held one meeting about them, in the last week of the project, attended by whoever had not already rolled off. That lived experience is what the exam is testing against, and it is why the timing distractors work so well.
We counted the options. Across the 2,141 questions here, 48 answer choices involve lessons learned. Twelve are keyed. Sort the 36 failures and one category swallows most of them.
Because it throws away the half of the value that belongs to this project.
The clearest case in the bank: an agile project is halfway through when the team learns two things. The original message-queue approach will not work, and a pivot costs two weeks but produces a stronger solution. Separately, running user training every three sprints rather than every sprint yields better feedback.
The keyed answer records both in the lessons learned register immediately. The three distractors are all reasonable-sounding delays:
| Option | Why it fails |
|---|---|
| "Wait until the end-of-project retrospective to document all the lessons comprehensively" | Forfeits the benefit to this project and reconstructs detail from memory |
| "Share the insights informally through casual conversations" | Leaves no record for anyone outside the conversation |
| "Finish the current deliverable first, then set aside time after release" | Makes capture compete with the next piece of work, a contest it usually loses |
Look at the second finding again. Training every third sprint produces better feedback, and the project has sprints left. Capture it now and the remaining iterations change. Capture it at the end and it is a note for somebody else's project.
The same logic keys a forming-stage question. A team is in the forming stage and the project manager wants it to improve as the project unfolds. "Hold a project post-mortem and capture lessons learned at the very end" is a distractor. The keyed answer holds a retrospective with the whole team at the end of each iteration and feeds those lessons into the next one. Short loops beat one long one, and a post-mortem captures lessons too late for this project to use.
Ownership, and whether the mechanism adds work.
One question has team members saying they have no time to update the lessons learned repository because their other responsibilities have grown. Four options:
The keyed answer costs nobody an extra meeting. That is the point. When a scenario tells you a team is overloaded, an answer that fixes the problem by adding a task is answering a different question.
Common trap: treating the lessons learned register as a closure artifact. Candidates file it mentally next to the final report and the contract closure checklist, so when a mid-project scenario offers "document it now" against "capture it comprehensively at the end," the tidier option wins. The bank keys against tidiness here consistently. There is a real closure step, and the bank keys it too: uploading the lessons learned register and the final report to the organization's central repository is the keyed answer in a closeout question. Recording during, transferring at the end. Two different actions, and the exam will hand you one dressed as the other. Because this bank explains each losing option rather than just marking it wrong, the end-of-project distractor stops being a near miss and becomes a shape you recognize.
One more distinction the bank tests directly: sprint reviews are for demonstrating the product, retrospectives are for lessons learned. A candidate who blurs those will lose questions that turn entirely on which event the scenario is describing.
When are lessons learned recorded on a project? Throughout, as they are identified, not collected at the end. A bank question about a mid-project pivot keys recording the lessons in the register immediately, because one of the findings changes how the remaining iterations are run.
Why is "capture lessons learned at the end of the project" usually a distractor? Because it forfeits the benefit to the current project entirely and reconstructs detail from memory after the team has moved on. Across this bank, lessons-learned options are keyed 12 times against 36 as distractors, and end-loading is the most common failure.
What is the difference between a retrospective and the lessons learned register? A retrospective is an event where a team inspects its way of working at the end of an iteration. The lessons learned register is the record that captures findings as they arise, from any source. One bank question keys the distinction directly: sprint reviews demonstrate the product, retrospectives handle lessons learned.
What happens to lessons learned at project closure? They move to the organization's repository so future projects can use them. One bank question keys uploading the lessons learned register and the final report to the central repository as part of closing out.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 Exam Content Outline, with every wrong answer explained rather than just marked wrong, so a lessons-learned distractor tells you whether it failed on timing, ownership, or workload. Start the free 20-question sample with no card and no signup.
Related: Continuous Improvement: Retrospectives, Lessons Learned, and What the Exam Actually Rewards and Closing a Project: The Steps Candidates Skip on the PMP Exam. The domain walkthrough is at /study/business-environment.
When are lessons learned recorded on a project?
Throughout, as they are identified, not collected at the end. A bank question about a mid-project pivot keys recording the lessons in the register immediately, because one of the findings changes how the remaining iterations are run.
Why is 'capture lessons learned at the end of the project' usually a distractor?
Because it forfeits the benefit to the current project entirely and reconstructs detail from memory after the team has moved on. Across this bank, lessons-learned options are keyed 12 times against 36 as distractors, and end-loading is the most common failure.
What is the difference between a retrospective and the lessons learned register?
A retrospective is an event where a team inspects its way of working at the end of an iteration. The lessons learned register is the record that captures findings as they arise, from any source. One bank question keys the distinction directly: sprint reviews demonstrate the product, retrospectives handle lessons learned.
What happens to lessons learned at project closure?
They move to the organization's repository so future projects can use them. One bank question keys uploading the lessons learned register and the final report to the central repository as part of closing out.