Capture what worked, what didn't, and the specific process changes it should trigger — before the team scatters to the next project.

Teams repeat the same mistakes because lessons learned are discussed once, informally, and never documented anywhere anyone will find them again. This template turns that hallway conversation into something that actually changes how the next project runs — schedule and budget variance, deliverables, what went well, what didn't, root cause analysis, and specific, owned process changes.

What's inside:

• A fully worked example showing real root-cause analysis, not just symptom-level complaints

• The same template in blank form, ready to fill in for your own project

• A Process Changes table with owners and status, so lessons become actions instead of just observations

• Guidance on running the review while it's still fresh, and on being specific enough that a lesson can actually be acted on

Built for PMO leads building an institutional learning practice, and project managers closing out a major initiative who don't want to make the same mistake twice.

Format: Word (.docx) — fully editable, works in Word, Google Docs, and most word processors.