2.2 Principle 2: Learn from Experience
Key Takeaways
- PRINCE2 project teams must explicitly seek, record, and apply lessons from previous projects, rather than relying on memory or informal practices.
- Learning occurs across three distinct temporal phases: When starting a project (seeking lessons), as the project progresses (recording lessons), and as the project closes (passing lessons on).
- Lessons must be actionable recommendations logged in the Lessons Log and formally compiled in the Lessons Report at project closure.
- Principle 2 prevents repeating past organizational mistakes and ensures proven positive techniques are embedded into future project practices.
- PRINCE2 7 emphasizes creating a learning culture and integrating human feedback mechanisms into knowledge management.
2.2 Principle 2: Learn from Experience
When starting and managing a project, human beings have a natural tendency to rely on immediate intuition or assume that every challenge encountered is completely novel. However, in almost every organization, similar projects have been executed in the past, encountering identical technical hurdles, vendor bottlenecks, or estimation errors. PRINCE2 Principle 2: Learn from Experience mandates that project teams actively seek out, document, and apply lessons learned throughout the entire project lifecycle.
PRINCE2 Principle Rule: PRINCE2 project teams learn from previous experience: lessons are sought, recorded, and acted upon throughout the life of the project.
Foundational Concept: Organizational Memory
Without a structured mechanism to capture and re-apply knowledge, organizations suffer from severe organizational amnesia. When key project personnel leave or move to other departments, their tacit knowledge is lost, causing future project teams to repeat costly mistakes.
PRINCE2 transforms learning from an informal, optional end-of-project exercise into a continuous, professional duty. In PRINCE2, taking time to review historical records is not an administrative burden; it is a risk-mitigation strategy that saves time and money.
The Three Temporal Phases of Learning
Learning in PRINCE2 is structured across three distinct phases in the project lifecycle:
+-----------------------------------------------------------------------------------+
| THE THREE PHASES OF LEARNING |
+-----------------------------------------------------------------------------------+
| 1. WHEN STARTING | Seek lessons from previous projects & external sources |
| 2. AS WE PROGRESS | Record new lessons as work is executed in stages |
| 3. WHEN CLOSING | Pass lessons on to corporate repositories for future use |
+-----------------------------------------------------------------------------------+
Phase 1: When Starting the Project (Seeking Lessons)
Before committing significant organizational resources to planning, the project team must investigate prior projects:
- Review Historical Artifacts: Inspect Lessons Logs, End Project Reports, and audit archives from past internal projects.
- Consult Stakeholders: Interview experienced Project Managers, Team Managers, suppliers, and subject matter experts.
- External Research: Look at industry benchmarks, academic literature, or external standard operating procedures.
- Application: Incorporate findings directly into the Project Brief, risk evaluation, and initial strategy management approaches.
Phase 2: As the Project Progresses (Recording & Acting on Lessons)
As work is executed across management stages, unexpected events (both positive and negative) will occur:
- When a risk materializes or an issue is resolved, the Project Manager evaluates why it happened.
- If a team discovers an innovative technique that accelerates delivery by 20%, that positive insight is captured.
- Lessons are actively logged in the Lessons Log and applied immediately to current and upcoming stage plans.
Phase 3: As the Project Closes (Passing Lessons On)
As part of the Closing a Project process, the Project Manager compiles a formal Lessons Report:
- The report aggregates all valuable insights gained during the project.
- It is submitted to the Project Board and passed to Corporate, Programme Management, or a Center of Excellence (PMO).
- This ensures future project teams can benefit from the project's experiences.
Management Products: Lessons Log vs. Lessons Report
A critical distinction in PRINCE2 Foundation exams is the difference between the dynamic repository (Lessons Log) and the formal snapshot report (Lessons Report):
| Feature | Lessons Log | Lessons Report |
|---|---|---|
| Type | Record (Dynamic Log) | Report (Formal Document) |
| Created In | Starting up a Project process | Initiating a Project / Closing a Project |
| Maintained By | Project Manager | Project Manager |
| Purpose | Continuously capture observations, issues, and ideas throughout the project lifecycle | Formally communicate compiled lessons to Project Board, Corporate, or PMO |
| Timing | Live repository updated constantly | Produced at Stage Boundaries (if needed) and mandatory at Project Closure |
| Audience | Current Project Manager, Team Managers, Project Assurance | Project Board, Corporate/Programme Management, Future Project Teams |
Anatomy of a Valid Lesson Learned
For a lesson to be useful, it must be actionable. Merely writing "Vendor delivery was slow" is an observation, not a lesson. A complete PRINCE2 lesson entry in the Lessons Log should detail:
- Event / Trigger: What occurred during project execution?
- Context: What were the circumstances surrounding the event?
- Root Cause: Why did it happen? (e.g., lack of penalty clauses in supplier contract).
- Impact: How did it affect time, cost, quality, scope, or safety?
- Action Taken: How was the immediate situation handled?
- Recommendation: What specific rule or practice should future projects follow to repeat the success or avoid the failure?
People and Cultural Dimension in PRINCE2 7
PRINCE2 7 explicitly connects Principle 2 to the People element. Capturing honest lessons requires an organizational environment built on psychological safety and open communication.
If an organization fosters a blame culture where admitting mistakes leads to professional punishment, project teams will conceal failures, ensuring the organization never learns from them.
Key People practices for Principle 2 include:
- Conducting blame-free retrospective workshops at stage boundaries.
- Encouraging cross-functional transparency where suppliers and users share candid feedback.
- Recognizing individuals who identify system flaws early.
Comparison Table: Active Learning vs. Passive Archiving
| Dimension | Passive Archiving (Poor Practice) | Active PRINCE2 Learning (Principle 2) |
|---|---|---|
| Timing | Done once at the very end of the project during cleanup | Integrated into setup, stage execution, and closure |
| Focus | Documenting excuses or assign blame for missed targets | Extracting generalizable recommendations for systemic improvement |
| Accessibility | Stored in obscure network folders that no one reads | Formally transferred to PMO repositories and reviewed at new project kickoff |
| Culture | Defensive, fear-driven, compliance-oriented | Transparent, psychologically safe, continuous improvement focused |
When should a PRINCE2 project team first seek out and review lessons learned from previous projects?
What is the primary operational difference between the Lessons Log and the Lessons Report in PRINCE2?
A project manager encounters an unexpected technical failure during stage execution, resolves it, and identifies a way to prevent it in future projects. Which action aligns best with Principle 2?