Most PMP candidates think of a lessons learned register as a closing activity. Something you fill out at the end of a project, mostly for show.
That assumption alone can cost you points on exam day.
The common mistake
Ask a room full of experienced project managers when a lessons learned register gets used, and most will say the same thing: at project closure.
It makes sense. In real life, "lessons learned" often does happen in a wrap-up meeting nobody wants to attend. A quick retro, a shared document, then everyone moves on.
But the exam isn't testing what happens in most offices. It's testing what the standard actually says. And the standard treats the lessons learned register as a living document, not a farewell letter.
Why this trips candidates up
According to the PMBOK 8th Edition, the lessons learned register is created early — as an output of the knowledge management activity near the start of a project. From that point, it gets used and updated more than once, at different moments across the project, not just at the end.
For example:
Risk: when a risk plays out differently than expected, the risk register gets updated with the new status — but the insight behind it (what caused it, what worked) goes into the lessons learned register.
Stakeholder engagement: if an engagement approach isn't working, the stakeholder register tracks the change in status — but what the team learned from it goes into the lessons learned register.
Communications: if stakeholders need different information than planned, the communications plan may be adjusted — but the reason why, and what was learned, goes into the lessons learned register.
It isn't sitting untouched in a folder until the project ends. It's being read and added to continuously, by the people doing the work — captured in whatever form is efficient, including notes, photos, or recordings.
What this means for the exam
Questions built around the lessons learned register are really questions about mindset. They're checking whether you see project knowledge as something to capture and use immediately, or something to file away for later.
The exam rewards the first mindset. When a question makes you choose between capturing knowledge now or waiting to document it later, "now" almost always wins.
This same logic extends to other documents candidates tend to mentally park at closing — the issue log, the risk register, the stakeholder register. All of them get updated repeatedly across processes throughout the project, not just at the end.
The takeaway
The lessons learned register isn't a closing formality. It's a working document that shapes decisions while the project is still in motion.
Once you see it that way, a whole category of exam questions gets easier — because you stop looking for the "closing" answer and start looking for the "right now" answer.
That shift, more than any formula or acronym, is what separates candidates who pass from candidates who almost do.
P.S. If you're preparing for the PMP, connect with me on LinkedIn if you haven't already — I'd love to hear where you are in your study: https://www.linkedin.com/in/vandersonbaril/
I would also be interested to hear where you are in your own PMP journey. While I may not be able to respond to every message, I do read all replies.
Thanks for reading, and see you next Saturday.
