Lessons Learned
Capture what worked, what didn't, and what to do differently, so the next team starts smarter. Try it in Elium.
The Lessons Learned Template gives your team a structured format to capture what worked and what didn't after any project or initiative. Document the insights while they're fresh, assign follow-up actions, and make them searchable for future teams. It's how you stop repeating mistakes and start compounding experience.
Category
Operations
What is it?
A lessons learned template is a structured document for recording the key insights from a project, initiative, or incident, including what went well, what went wrong, why it happened, and what the team recommends doing differently next time. It turns experience into organisational knowledge that future teams can access and apply.
Most organisations repeat the same mistakes because lessons are never captured, or captured but never found. Project teams move on to the next delivery, and the knowledge from what they just completed stays in their heads. A standardised template ensures that lessons are documented consistently, stored where others can find them, and structured in a way that makes them actionable rather than anecdotal.
Who should use this template?
This template is for teams responsible for continuous improvement:
-
Project Managers: document project lessons at close-out so future projects benefit from the experience
-
Operations Managers: capture process improvements after incidents or changes
-
Team Leads: facilitate lessons learned sessions after sprints, milestones, or events
-
Knowledge Managers: ensure lessons are stored in a searchable, centralised format that future teams can access
How to create this template in Elium
-
Open the Template Builder: Go to your profile menu and select the Template Builder tab, or click “+ Create” and choose “Create a new template”.
-
Set the scope: Choose an icon, enable the template, and decide whether it applies platform-wide or to specific spaces (e.g. Project Management or Operations).
-
Add structured fields: Click “Field” to add metadata: text fields for project name and department, a user field for lessons author, a date field for session date, and a tag field for project phase (pre-populate with “Planning”, “Execution”, “Close-out”, “Post-incident”). Mark project name and session date as mandatory.
-
Build the lessons structure: Use the “+” button to add content blocks: a text block for context, text blocks for what went well and what went wrong, a table block for recommendations (columns: recommendation, priority, owner, deadline), a text block for key metrics, and a links block for related documents.
-
Preview and save: Review the template layout, then save. Project managers can now select it when running close-out sessions, and you can apply it to existing content in bulk.
How AI helps
Capture faster. Paste your meeting notes, retrospective boards, or email discussions into Elium’s AI. It categorises feedback into successes, failures, and recommendations, so the facilitator organises rather than transcribes.
Retrieve smarter. A project manager starting a new construction project asks Elium’s AI: “What lessons did we learn from the Lyon metro tunnelling phase?” The AI returns the specific successes, failures, and recommendations from that project, so proven improvements are applied from day one.
Why teams use Elium for this
Lessons learned sessions happen, but the documents they produce often disappear. They are filed in a project folder, never tagged, and never found by the next team facing the same challenge. Elium solves this by making lessons searchable and contextual: structured templates ensure consistency, tags and metadata make lessons discoverable, and AI-powered search lets anyone find relevant experience from a plain question.
Bouygues Construction, with 53,500 employees across 80 countries, uses Elium to centralise project knowledge including lessons learned, procedures, and best practices. When a team in one country encounters a challenge, the solution from a previous project in another country is one search away.
Common questions about lessons learned templates
Lessons learned are documented insights from a project or initiative: what worked, what failed, and what to change next time. Without capturing lessons, organisations repeat the same mistakes and miss opportunities to replicate successes. Structured documentation ensures experience becomes organisational knowledge rather than individual memory.
A complete lessons learned template includes project metadata (name, date, team, phase), context about objectives and outcomes, sections for what went well and what went wrong with root causes, actionable recommendations with owners and deadlines, key metrics, and links to related project documents for context.
Documented lessons prevent repeated mistakes because future teams access proven solutions. They accelerate project planning because managers start with real experience. They improve estimation accuracy because historical data informs forecasts. They build a culture of continuous improvement where learning from failure is expected.
Focus on specifics, not generalities: “the procurement timeline was two weeks too short” is actionable, “planning could be better” is not. Include root causes, not just symptoms. Tie every recommendation to a named owner and deadline. Conduct the session while details are fresh, ideally within a week of the milestone or close-out.
Lessons learned typically document insights at project close-out for the benefit of future projects across the organisation. A retrospective is usually held at the end of a sprint or iteration, focused on the team’s own working practices and immediate improvements. Lessons learned look outward; retrospectives look inward.
Try this template in Elium
See it on your own knowledge.
Customise it to fit your team's workflow. Get started for free.