Lessons Learned Template
Capture what went well and what didn't at the end of a project, so the next one benefits. A clear structure turns experience into knowledge the whole team can use.
Free to start · Swiss-made · GDPR compliant
Turning project experience into lessons learned
The Collaboard template guides the team from left to right: a backlog with a deck of notes, a diagram with success and failure on the vertical axis and planned and unplanned on the horizontal axis, and an Improvement Actions area. Prepared cards for What, Who and Until when make it easy to turn lessons into concrete actions, and instructions on the left explain the four steps.
Collect lessons
Invite the team and record lessons learned from the last project or quarter in the Backlog area, one per note.
Sort them
Move each card from the backlog into the diagram: was it a success or a failure, planned or unplanned?
Find root causes
Discuss each lesson: what caused it, what were the consequences and what could be improved?
Define actions
Write suggestions in the Improvement Actions area, using the prepared What, Who and Until when cards.
Prioritize
Focus on a few actions with the biggest effect, rather than one per lesson.
Share the lessons
Store the board where future project teams can find it, and review the actions at the next milestone.
What is a Lessons Learned session?
Lessons learned are insights a team gains from a project or a period of work, from what went well and from what went wrong. The Collaboard template sorts them on two axes, success or failure and planned or unplanned, and turns them into improvement actions with a clear owner and date.
The four quadrants of the template
The examples follow one illustrative scenario: a team looking back on a website relaunch.
- Planned and successful What went as intended. Example: the launch date was met.
- Unplanned and successful Positive surprises. Example: a new testing tool saved two weeks.
- Planned and failed Plans that didn't work out. Example: the content migration took twice as long as estimated.
- Unplanned and failed Problems nobody saw coming. Example: an external service changed its interface.
For a shorter look back after a sprint, Start Stop Continue is quicker.
Moments to hold a lessons learned session
- Project closings Capture what the team learned before everyone moves on.
- Quarterly reviews Look back on a quarter and plan improvements for the next one.
- After incidents Learn from a problem once the immediate pressure is over.
- Knowledge transfer Pass on experience to teams starting similar projects.
Learning from successes and the unplanned
- Include successes Lessons learned are not only about mistakes. Successes show what to repeat.
- Look at the unplanned Unplanned successes and failures often hold the most useful lessons.
- Focus on causes Describe what happened and why, without blaming people.
- Make actions concrete Every action needs a what, a who and an until when, as the prepared cards suggest.
Why Collaboard
A Swiss-made online whiteboard for teams that care where their data lives.
Your data stays in Europe
Choose hosting in Switzerland, Germany or the EU, fully GDPR compliant. Or run Collaboard on your own servers.
Invite anyone with a link
Guests join your board for free, right in the browser. Nothing to install, no extra licenses for participants.
Made in Switzerland, with real support
Collaboard is developed in Switzerland. When you need help, you talk to people who know the product.
Frequently asked questions
Is the Lessons Learned template free?
Yes, the Lessons Learned template is free to use with a Collaboard account. The free plan includes up to 3 boards and five people per session.
What are lessons learned?
Lessons learned are insights a team gains from a project, from what went well and from what went wrong. They are documented so future projects can benefit.
When should a Lessons Learned session take place?
A Lessons Learned session should take place at the end of a project or a major phase, ideally within a few weeks, while the experiences are still fresh.
Who should take part in a Lessons Learned session?
A Lessons Learned session includes the core project team and, where useful, stakeholders, sponsors or other teams involved in the project.
How do I document lessons learned?
Lessons learned can be documented directly on the board. Keep the board as a record or export it as an image or PDF, and store it where future project teams can find it.
Start your next whiteboard now
Get a free trial of Collaboard with up to 3 boards and five people per session. All key features are available for you to try out.
