Governance · tool 13 of 14
Lessons Learned
Lessons Learned: turns one project’s pain into the next project’s head start.
Best for: Throughout, not just at the end · Time: 1 hour
Domain: Governance · Focus area: Closing
How it works
Most lessons die in a document nobody opens. A useful lesson is specific, says what to do differently and reaches someone who can act on it. Capture them through the project, while memories are fresh.
- Write “next time do X”, not “communication was poor”.
- Give each lesson an owner.
- Change a template or checklist so that the lesson sticks.
How to apply it
- Hold a short review at each milestone.
- Ask what worked, what didn’t and what to change.
- Turn the top three into actions with owners.
- Update a shared checklist.
“Book the penetration test six weeks before launch; we left two and lost a month.” That line then goes into the launch checklist.
Read the previous project’s lessons at kick-off. That’s when they’re worth something.
Use it
- Template: Lessons Learned (blank), filled example
- Playbook: I inherited a failing project
Quick check
Which is a useful lesson?
Sources
- PMBOK® Guide, 8th edition, and The Standard for Project Management (PMI, 2025)
Last reviewed 2026-11-02 against the PMBOK® Guide, 8th edition · Practitioner review pending · How this guide is made