
Lessons Learned: Knowledge Gained for Future Performance Improvement
PMBOK v8 Definition
Lessons learned is defined as "the knowledge gained during a project that shows how project events were addressed or should be addressed in the future for the purpose of improving future performance." This concept belongs to the Project Knowledge Management domain and is a key output of the Manage Project Knowledge process within the Executing Process Group and Project Knowledge Management Knowledge Area.
Why It Matters for the Exam
The PMI exam frequently tests lessons learned because it is one of the most misunderstood yet critical knowledge management concepts. Questions appear in situational scenarios where you must distinguish between when lessons are collected (throughout the project vs. only at the end) and how they are used (for immediate improvement vs. future projects). Expect 2-4 questions on this topic, primarily in situational and "what should the PM do next" formats.
Key Points to Remember (for the exam)
- Primary Purpose: Lessons learned show how project events were addressed or should be addressed in the future for improving future performance
- Timing: Lessons learned/retrospectives are managed throughout the project, not only at the end
- Knowledge Integration: Project teams ensure that project and organizational knowledge and learning are combined to manage project deliverables and value
- Documentation Tool: Lessons learned are recorded in a log (a document used to record and describe selected items identified during execution of a process or activity)
- Relationship to Tacit Knowledge: Lessons learned help convert tacit knowledge (personal, embedded, experience-based, challenging to transfer) into explicit knowledge
- Common Confusion: Many think lessons learned are only a closing activity; PMBOK v8 emphasizes they are ongoing processes incorporated during the project
- Output Type: Lessons learned are both an output of Manage Project Knowledge and an input to future planning and execution
Typical PMI Exam Example
A project manager is halfway through a software development project. The team has encountered several integration issues that were resolved with creative solutions. What should the project manager do to ensure this knowledge benefits the organization?
Correct answer: Document the lessons learned immediately and incorporate them into ongoing processes, ensuring the team uses this knowledge to improve current and future project performance.
PMI Exam Traps
-
Trap: Thinking lessons learned are only collected at the end of the project Reality: Lessons learned/retrospectives are managed throughout the project, not only at the end
-
Trap: Confusing lessons learned with the lessons learned register Reality: The lessons learned is the knowledge gained; the log is the document used to record and describe selected items
-
Trap: Believing lessons learned are only for future projects Reality: Lessons learned are incorporated during ongoing processes to improve current project performance
-
Trap: Assuming all knowledge is explicit and easily documented Reality: Much knowledge is tacit (personal, embedded, difficult to articulate, experience-based, challenging to transfer) and requires deliberate management
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Knowledge | Input to lessons learned process | Knowledge is "a mixture of experience, values and beliefs, contextual information, intuition, and insight" used to make sense of new experiences |
| Manage Project Knowledge | Process that produces lessons learned | Managing knowledge involves more than just documenting explicit knowledge or obtaining lessons learned at the end |
| Log | Documentation tool | A log is used to record and describe selected items identified during execution of a process or activity |
| Tacit Knowledge | Knowledge type to capture | Tacit knowledge is personal, embedded, difficult to articulate, experience-based, and challenging to transfer |
| Retrospectives | Similar concept | Meetings for lessons learned and retrospectives are examples of project meetings |
Quick Review Questions
-
A project manager is nearing project completion. The sponsor asks for a lessons learned document. What should the project manager respond regarding the timing of lessons learned collection?
-
During a project, a team member shares a valuable insight about a workaround that saved significant time. The project manager wants to ensure this knowledge is available for other teams. What should the project manager do?
-
What is the primary difference between explicit knowledge and tacit knowledge in the context of lessons learned management?
-
A project manager is creating a document to record issues, changes, and assumptions identified during project execution. What is this document called according to PMBOK v8?
-
The project team has completed a retrospective and identified several lessons. How should these lessons be used according to PMBOK v8?
PMBOK v8 Reference
Section 4.5 - Manage Project Knowledge (Executing Process Group, Project Knowledge Management Knowledge Area)
Key definitions from the PMBOK v8 Glossary:
- Knowledge: A mixture of experience, values and beliefs, contextual information, intuition, and insight that people use to make sense of new experiences and information
- Lessons learned: The knowledge gained during a project that shows how project events were addressed or should be addressed in the future for the purpose of improving future performance
- Log: A document used to record and describe or denote selected items identified during execution of a process or activity