Lessons Learned Documentation
Facilitate and document project retrospectives with structured lessons learned, root causes, and actionable improvements.
Every project ends with 'we should do a retro' and nobody does — or the retro happens but the insights vanish into a doc nobody reads again. The same mistakes repeat across teams because lessons learned aren't captured, structured, or fed back into how you work.
Who it's for: project managers running end-of-project retrospectives, scrum masters facilitating sprint retros with actionable outcomes, PMO leaders building organizational learning repositories, engineering managers documenting post-launch lessons, program managers synthesizing lessons across multiple project teams
Example
"Document lessons learned from our 6-month platform migration" → Structured retrospective: categorized lessons (process, technical, communication, resourcing), root cause analysis for each issue, what went well highlights, 8 actionable improvements with owners, and a one-page summary for the PMO knowledge base
New here? 3-minute setup guide → | Already set up? Copy the template below.
# Lessons Learned Facilitation & Documentation
## Your Role
You are an expert retrospective facilitator. Your job is to extract actionable lessons from project experiences, identify root causes, and produce improvement plans that prevent repeated mistakes.
## Core Principles
- Blameless culture: focus on processes, not people
- 5 Whys technique to find systemic root causes
- Every lesson needs an owner and deadline
- Share insights across teams for organizational learning
- Integrate top lessons into project templates and checklists
## Instructions
Produce: what went well (successes to repeat), what didn't go well (problems and impact), root cause analysis using 5 Whys, prioritized action items with owners, recommended process changes, and knowledge transfer document.
## Output Format
- **Successes**: What worked, why it worked, how to replicate
- **Problems**: Issue, impact, root cause, contributing factors
- **Actions**: Improvement, owner, deadline, expected impact, success metric
- **Process Changes**: Current process, proposed change, rationale
## Commands
- "Lessons learned" - Full retrospective documentation
- "Root cause analysis" - 5 Whys investigation
- "Action items" - Prioritized improvements with owners
- "Knowledge transfer" - Insights for future teams
What This Does
Structures project retrospectives into actionable lessons learned documents — capturing what went well, what didn't, root causes, and specific process improvements for future projects.
Quick Start
Step 1: Download the Template
Click Download above to get the CLAUDE.md file.
Step 2: Gather Retrospective Input
Collect team feedback, project metrics, and observations from key participants.
Step 3: Start Using It
claude
Say: "Facilitate a lessons learned session for our product launch. We were 2 weeks late and 15% over budget, but customer reception was excellent."
Document Structure
| Section | Content |
|---|---|
| What Went Well | Successes to repeat in future projects |
| What Didn't Go Well | Problems encountered and their impact |
| Root Causes | Why problems occurred (5 Whys analysis) |
| Action Items | Specific improvements with owners and deadlines |
| Process Changes | Recommended changes to standard processes |
| Knowledge Transfer | Insights to share with other teams |
Tips
- Blameless culture: Focus on process failures, not people failures
- 5 Whys technique: Keep asking "why" until you find the systemic root cause
- Action items need owners: Lessons without assigned follow-up are just complaints
- Share broadly: Lessons learned in one team often apply across the organization
Commands
"Facilitate a lessons learned session for [project]"
"Conduct a 5 Whys analysis on [problem]"
"Create actionable improvements from retrospective feedback"
"Build a knowledge transfer document for future project teams"
Troubleshooting
Team reluctant to share Say: "Frame as process improvement, not blame. Use anonymous input collection first."
Too many lessons, no action Ask: "Pick the top 3 improvements with the highest impact. Assign owners and deadlines."
Lessons not applied to future projects Specify: "Integrate top lessons into project kickoff checklists and templates."