itsual Lessons Learned
Overview
Lessons learned documents turn experience into organizational memory. They focus on what to repeat, what to change, and what to avoid.
When to Use
- Project closeouts
- Post-incident or post-mortem follow-up (document form)
- Major initiative retrospectives
- Program or portfolio reviews
Recommended Structure
- Context (project/initiative, timeframe, goals)
- What went well
- What did not go well
- Root causes or contributing factors
- Recommendations (specific and actionable)
- Owners and follow-up for systemic changes
- Appendix (data, timeline, references)
Principles
- Be honest and specific — generic lessons are useless
- Focus on systems and processes, not personal blame
- Turn observations into recommendations with owners
- Share widely enough that others can benefit
- Revisit whether previous lessons were actually applied
Verification
- Lessons are specific enough to act on
- Recommendations have clear owners or next steps
- Both successes and failures are covered