This document outlines lessons learned processes and provides recommendations for capturing lessons learned. It discusses integrating lessons learned routinely into daily work to avoid extra costs and forgetting key points over time. When capturing lessons learned, the document recommends focusing on what went well, what didn't go well or had unintended consequences, what would be done differently if starting over, and recommendations for others undertaking similar projects.

1. LESSONS LEARNED
Glen Grant

2. Lessons Learned Rhythm
• Define the area of work/project/problem
• Collect the information
• Verify and synthesize
• Store
• Disseminate
• Discuss and cost
• Agree changes
• Change

3. Process
• Integrated approach
– Routine and regular or “as it happens” capture
– Part of daily work
– No extra costs
– Significance may not be apparent at the time
• Post project approach
– Big project at the end
– Extra to daily work
– Extra costs
– May miss key points forgotten by time

4. Whatever method you are using,
concentrate on obtaining information in
four general areas:
1. What went well?
2. What didn't go well or had unintended
consequences?
3. If you had it all to do over again, what would you do
differently?
4. What recommendations would you make to others
doing similar projects?