Lessons Learned
Documented insights captured during and at the end of a project that describe how events were handled and recommend how similar situations should be managed in the future to improve performance.
Key Points
- Collected throughout the project and at closeout, covering both successes and problems.
- Each entry should include context, what happened, its impact, and a clear recommendation.
- Stored in an organizational repository so future teams can find and apply them.
- Used to update plans, processes, risk responses, and training for continuous improvement.
Example
On a facilities upgrade project, equipment delivery was delayed due to underestimated lead times. The team records a lesson: verify vendor lead times during planning, add a two-week buffer, and include a procurement checklist for future projects. This is added to the company repository and referenced by the next project team.
PMP Example Question
Which action best ensures lessons learned improve outcomes on future projects?
- Hold a structured review at closeout and store categorized lessons in a central repository.
- Archive only the final schedule and budget without additional context.
- Email a brief summary to the sponsor and delete working files.
- Wait until a major issue occurs before documenting any takeaways.
Correct Answer: A — Hold a structured review and store lessons in a central repository
Explanation: A creates accessible, organized knowledge that future teams can reuse; the other options limit availability or omit needed detail.