What is a lessons learned template?

A form for recording what a project, event or incident taught the team: what happened, why, the lesson written as what the next team will do, and any action with an owner and a date.

When should you hold a lessons learned session?

Within a week of the end of the event, project phase or incident, while people still remember the order of events and the reasons. Forty-five minutes is enough for a kaizen event or a small project.

What is the difference between lessons learned and root cause analysis?

Root cause analysis finds why a specific problem happened so it can be fixed. A lessons learned session looks back over a whole piece of work, good and bad, and records what the next team should do differently. An incident can have both.

How do you make sure lessons are used?

Put them where the next team will look, such as the project start checklist, the event charter or the standard work, give each action one owner and a date, check the actions at 30 days, and share relevant lessons with other lines and sites.

What makes a good lesson?

It is specific, it is something the next team can do, and it is tied to a reason. Stage the parts on a cart before the changeover starts is a lesson. Be better prepared is not.

Free template

Updated November 6, 2026

Lessons learned template

A lessons learned template is a form for recording what a project, kaizen event, incident or launch taught the team, written so the next team can use it. Each row holds what happened, why it happened, the lesson as something the next team will do, and, where it needs work, an action with an owner and a due date. This one has a one-page log to fill in during a 45 minute session, a facilitator's guide with an agenda and ground rules, and an Excel register that shows which actions are done, open or overdue and which lessons were shared with other areas.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Page 1 of the lessons learned template — Eight-row lessons logWent well or wrongWhy it happenedLesson and actionOwner and due date45 minute session guideStatus and shared flag

Filled-in Lessons learned template: a changeover kaizen event with six lessons — The same sheet filled in with the worked example (page 3 of the PDF, illustrative numbers). Open full size (opens the picture in a new tab)

When to use it

When to use a lessons learned template

After a kaizen event, while the team still remembers the days and before the room is needed for something else.
At the end of a project phase, before the next phase starts and the people move on.
After an incident, near miss or audit finding, once the facts are known, to record what the team learned alongside the corrective action.
After a product or line launch, to hand the next launch team a list that was written by the people who did it.
Not in place of root cause analysis. Use the RCA tools for a problem that is still open, and this for what the team learned from the work.

How to fill it in

1
Hold the session within a week
Forty-five minutes, in the room where the work was done, with the people who did it. Bring the plan, the data and the original charter.
2
Set the frame
State the aim and the facts: what was planned, what happened, the dates. Agree to talk about the work and the system, not about people.
3
Ask what went well, then what went wrong
Everyone adds one thing before anyone adds a second. For each item ask why until you reach something the team controls.
4
Write each one as a lesson
A lesson is a statement the next team can act on, such as stage the parts before the changeover starts. Mark each row as went well or went wrong and give it a category.
5
Give every action an owner and a date
If a lesson needs work, one named person owns it and it has a due date before anyone leaves. Read the sheet back to the room.
6
File it where the next team will look, and check at 30 days
Type the sheet into the register within two days, add the lessons to the project start checklist or the standard work, and review the actions at 30 days.

The session

A 45 minute lessons learned session

A fixed agenda keeps the session short and stops it turning into a debate about one problem.

Minutes	Step	What to do
0 to 5	Set the frame	State the aim and the facts. No blame. The scribe writes on the sheet.
5 to 15	What went well	Each person adds one thing. Ask what made it work, so it can be repeated.
15 to 30	What went wrong	Facts first, then ask why until you reach something the team controls.
30 to 40	Turn each into a lesson	Write it as what the next team will do. Decide which lessons need an action.
40 to 45	Owners and dates	Every action gets one named owner and a date. Read the sheet back before anyone leaves.

0 to 5
Step
Set the frame
What to do
State the aim and the facts. No blame. The scribe writes on the sheet.
5 to 15
Step
What went well
What to do
Each person adds one thing. Ask what made it work, so it can be repeated.
15 to 30
Step
What went wrong
What to do
Facts first, then ask why until you reach something the team controls.
30 to 40
Step
Turn each into a lesson
What to do
Write it as what the next team will do. Decide which lessons need an action.
40 to 45
Step
Owners and dates
What to do
Every action gets one named owner and a date. Read the sheet back before anyone leaves.

A filled-in example

Illustrative, not a benchmark

An example (illustrative): a case packer changeover kaizen event on line 1, 14 to 16 October 2026, with the session on 19 October and the status shown as at 2 November.

The session logged 6 lessons: 1 went well and 5 went wrong. The one that went well, operators running the changeover from a video of the best run, has no action. It is marked Keep.
The other 5 each have an action, an owner and a date. Two are Done: the staging cart for change parts (lesson 2) and the kickoff checklist with a sponsor confirmation (lesson 3).
Lesson 4 is Overdue. The baseline came from the shift board and was 8 minutes better than a stopwatch run. The re-timing was due on 28 October and is not done.
Lessons 5 and 6 are Open and not yet due: update the standard work sheet and train all three shifts (due 6 November), and keep a tracker on the line for 30 days (due 13 November).
Done % = 2 ÷ 5 = 40%. Lessons 2 and 5 apply to the other packing lines, so they were passed on to lines 2 and 3.

The next event on that line starts with the staging cart, a charter that names the sponsor, and a stopwatch baseline, and the one overdue action is visible instead of buried in a report.

Common mistakes

Writing what went wrong and stopping there
A list of problems helps nobody. Each row needs the lesson, written as what the next team will do.
Holding it weeks later
People forget the order of events and the reasons within days. Hold it within a week.
Actions with no owner or date
An action without one named person and a date is a wish. Settle both before the session ends.
Filing it where nobody looks
A lesson that lives only in a report is forgotten by the next team. Put it in the checklist, the charter or the standard work they will use.
Making it about people
The session finds what in the system let the problem happen. Once it turns on blame, people stop being honest.

Download the template

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Run this template in LeanSuite

In LeanSuite a validated Kaizen is turned into a standard and shared with every plant, and each plant marks it applicable, implemented or not applicable with a reason, so adoption is tracked plant by plant.

See it in a 45-minute demo

In the lean glossary

Free tools

All free lean calculators

Guides

FAQ