Lessons Learned
Capture what worked, what did not, and why — to improve performance on future initiatives.
Definition
Lessons Learned is a technique used to capture insights, observations, and recommendations from a completed initiative or phase so that future work benefits from the experience. It focuses on what worked well, what did not, why outcomes occurred, and what should be done differently. When consistently applied, it is one of the most direct drivers of organizational delivery maturity.
Inputs
- Project or phase outcomes, retrospective notes, and team observations
- Stakeholder feedback from across the delivery lifecycle
- Performance data, incident reports, and risk registers
- Prior lessons learned registers for comparison
Outputs
- A documented lessons learned register with findings categorized by theme
- Specific recommendations for process, tooling, or approach improvements
- Inputs to future project planning, risk identification, and team onboarding
- An organizational knowledge asset for delivery improvement
When to Use
- At project or phase closure as a structured retrospective
- After major milestones or delivery events
- Following incidents, failures, or significant scope changes
- During retrospectives in agile delivery — the sprint retrospective is lessons learned in cadence
When Not to Use
- When the team is unavailable or unwilling to participate honestly
- When findings will not be reviewed or acted upon — capture is only valuable if it feeds improvement
- As a one-time exercise without a mechanism to share findings with future teams
See this technique in action with a free RequirementsHub workspace.
Start Free Workspace →