This guide covers everything you need to know about lessons learned updates in PMBOK 8. Lessons learned updates are the finalized, curated knowledge artifacts submitted to the organizational process assets repository at project closure — the bridge between project-level learning and organizational-level improvement.
What Are Lessons Learned Updates?
Lessons learned updates are the refined, approved, and formatted versions of the lessons captured in the lessons learned register, prepared for submission to the organization’s knowledge management system at project closure. While the lessons learned register is a living project document maintained throughout execution, the updates represent the final, vetted knowledge that the organization retains permanently.
The update process involves reviewing all lessons in the register, selecting the most impactful and generalizable ones, standardizing their format for the organizational repository, and getting sponsor or PMO approval before submission. Not every lesson warrants submission to the organizational database — the update process filters for lessons with the broadest applicability and clearest recommendations.
Lessons learned updates are what ensure that the knowledge gained on Project A actually improves how Project B is run — provided the organization has a functioning knowledge management system and project managers actually consult it during planning.
Lessons Learned Updates in PMBOK 8 — Domain and Process
In the PMBOK Guide 8th Edition, lessons learned updates belong to the Governance Performance Domain and are produced during the Close Project or Phase process. PMBOK 8 treats the submission of lessons learned updates to organizational process assets as a mandatory closure activity, not an optional add-on.
Lessons learned updates connect to the final report — the final report summarizes key lessons for stakeholders, while the updates provide the detailed, actionable records for the organizational knowledge base.
Key Elements of Lessons Learned Updates
Well-structured lessons learned updates typically include:
- Project Reference — project name, ID, PM, dates, and scope summary for context
- Category and Subcategory — standardized taxonomy matching the organizational knowledge base
- Situation Description — factual account of what happened, with enough context to be understood without project-specific knowledge
- Impact Assessment — quantified or qualified description of the effect on project outcomes
- Recommendation — specific, actionable guidance for future projects
- Applicability — types of projects or conditions where this lesson is most relevant
Lessons Learned Updates Example — Project Phoenix
At Project Phoenix closure, Alex Morgan reviewed the 18-entry lessons learned register and selected eight lessons for submission to MCG’s organizational knowledge base. The most significant submission was a detailed lesson on vendor contract structuring: the fixed-price SOW with BrightFrame eliminated design cost uncertainty and enabled a more accurate cost baseline. The submission included specific contract clauses that enabled this outcome and a template recommendation for future design vendor engagements.
A second submitted lesson covered the resource emergency protocol gap — with a specific recommendation to add an emergency resource replacement procedure to MCG’s standard resource management plan template. Riley Park reviewed and approved all eight submissions on May 15, 2024, and Alex uploaded them to MCG’s SharePoint lessons learned library, tagged by project type (website launch), domain, and project size.
You can download the complete filled-in example below — it shows exactly how lessons learned updates were prepared and submitted from a real project.
Download Free Lessons Learned Updates Template and Example
We have prepared two free resources to help you prepare lessons learned updates for your own projects:
- Download the Lessons Learned Updates Template — PMBOK 8 (blank, ready to fill in)
- Download the Lessons Learned Updates Example — Project Phoenix (filled in for a real $72K website launch)
Both are free downloads — no registration required.
Lessons Learned Updates — Best Practices and Common Mistakes
Curate the updates rather than submitting everything — a knowledge repository overwhelmed with low-quality entries becomes unusable. Standardize the format to match the organizational taxonomy so that lessons are searchable and findable by future project managers. Get sponsor sign-off before submission to confirm accuracy and organizational relevance.
The lessons learned updates process is most effective when the organization has a functioning knowledge management system and a culture where project managers actively consult lessons from past projects during planning. Teams that skip or rush this closure activity waste the learning investment made throughout the project.
Want to master project management with PMBOK 8? The PMBOK Guide 8th Edition is the definitive reference. Get your copy and use it alongside these free resources.
Free Template & Filled-In Example
Apply what you’ve learned with these two free resources:
- Download the Free Lessons Learned Updates Template (PMBOK 8) — Ready-to-use blank template for your next project.
- Download the Filled-In Example — Project Phoenix — See exactly how this document was completed for a real $72K website launch project.
Project Management