lessons learned template
Capture what went well, what didn't, and what to do differently, by workstream, with owner for follow-up.
Lessons learned exercises are almost always done badly. They are scheduled too late (after the team has dispersed), written as bland generalities ("communicate more"), and never actioned. This template is structured to make them genuinely useful.
It captures lessons per workstream rather than at project level, separates "what happened" from "why" from "what to do differently", and assigns an owner and a target follow-up date. Lessons without owners are noise.
In Pocket PMO, every project automatically generates a draft lessons-learned report from the project log, RAID closures, and change requests. The PM edits, validates with the team, and publishes to the organization's knowledge base.
What's inside
- •Workstream-level breakdown (not just project-level)
- •Three columns: what happened / why it happened / what to do next time
- •Owner and target date for every recommendation
- •Organisation-level vs project-level categorisation
- •Distribution list for sharing
When to use it
- •End of stage / phase (not just project end)
- •After a significant incident or recovery
- •Programme close-down
- •Quarterly PMO retrospective
Template structure
Every section below appears in the downloadable PDF as a ready-to-fill table.
Workstream
What worked
What didn't work
Organisational lessons
Use it live in Pocket PMO
The PDF is fine. The live version is better: auto-fill from your project, full audit trail on every change, AI Project Team drafts the tricky sections, and steering committees see one canonical version, not a stale spreadsheet copy.