This Lessons Learned example shows how Alex Morgan, PMP, captured what worked, what didn't, and what MCG should do differently in future projects — at the conclusion of Project Phoenix, a $72,250 website launch managed using the PMBOK Guide 8th Edition. This is a fully completed lessons learned document, not a blank template — it shows the depth of reflection that distinguishes high-performing project teams from those that repeat the same mistakes.

What Is a Lessons Learned Document?

A Lessons Learned document captures knowledge gained during a project that can improve performance on future projects. It covers both positive lessons (what worked well and should be repeated) and negative lessons (what went wrong and how to prevent it). In PMBOK 8, lessons learned are addressed within the Uncertainty and Measurement Performance Domains, and the Lessons Learned Register is a key project document maintained throughout execution — not just at closure. The lessons learned document produced at project close is a synthesis of those iterative captures, distilled into actionable recommendations for the organization's project management knowledge base.

What's Inside This Lessons Learned Example

This Lessons Learned example for Project Phoenix includes:

• Planned versus actual performance summary: delivered June 13, 2025 (on schedule), at $62,250 actual versus $72,250 approved — $10,000 under budget
• What went well: the placeholder content strategy (introducing dummy content in the CMS from Week 4 onward) prevented a full content-delivery delay from becoming a critical path issue; the team's agile sprint structure within a predictive framework allowed scope recovery without a formal re-baseline
• What could be improved: the IT department's involvement in the hosting migration (ISS-005) was not engaged early enough — an 11-day delay resulted from a conflicting infrastructure upgrade window that could have been identified and avoided in the planning phase
• Risk management performance: 12 risks identified at kickoff; 7 materialized as issues; all 7 resolved within contingency budget and without extending the schedule
• AI insight: Sam Lee used GitHub Copilot throughout the development phase, estimating a 15% reduction in coding time for repetitive backend tasks — a productivity gain MCG should formalize in future development projects
• Ten actionable recommendations for future web projects, including involving IT infrastructure teams in planning sessions and building multi-session CMS training into the scope from the outset

How Alex Morgan Used This Lessons Learned Document

Alex Morgan facilitated a 2-hour retrospective session with the full Project Phoenix team on June 16, 2025 — the day after go-live — to capture lessons while the experience was still fresh. The session used a structured Start/Stop/Continue format, with each team member contributing observations before the group synthesized them into the final recommendations. The completed document was submitted to MCG's PMO repository on June 20, making it available to any project manager planning a future web or digital transformation project. Riley Park specifically requested that the IT coordination lesson be escalated to the Operations Director as a process improvement recommendation.

Download and Customize

This Lessons Learned example is available as a free download. Use it as a reference to build your own lessons learned document, or start with the blank template and fill it in for your project.

• Download the Lessons Learned Template — PMBOK 8 (blank, ready to use)
• Read the article: Lessons Learned in PMBOK 8 — Guide and Best Practices

Lessons Learned Example: Key Takeaways

The most important insight from this Lessons Learned example is that lessons are only valuable when they lead to change. Alex Morgan did not just document the IT coordination failure — she formally escalated it as an organizational process improvement request. That distinction between capturing a lesson and acting on it is the difference between a lessons learned document that sits in a folder and one that actually improves the next project. Project Phoenix delivered on time and under budget despite seven issues materializing, because the team had access to lessons from MCG's previous projects and were disciplined enough to apply them throughout execution.

Want to go deeper? The PMBOK Guide 8th Edition is the definitive reference for modern project management. Get your copy and use it alongside these examples to build a solid, practical understanding of every performance domain.