Lessons Learned Log: What It Is, How to Write One, and a Free Template

What Is a Lessons Learned Log?

A lessons learned log is a written list of what a project, event or piece of work taught you. Each entry says what happened, why, and what to do differently next time. The log is for the next team, which may be you in a year.

When You Need One and Who Reads It

You need a log when work ends, or at a natural pause in long work, and you do not want the same trouble to repeat. The readers are people planning something similar who were not there. Write for them.

What Goes in a Lessons Learned Log

1. The Work in One Line. What the project set out to do.
2. What Happened. Plain facts, in order.
3. What Went Well. Things worth repeating.
4. What Got in the Way, and Why. The cause, kept apart from the story.
5. One Change to Try. One for each problem, with an owner role.
6. What Is Still Unknown. Questions the notes could not answer.

How to Write a Lessons Learned Log, Step by Step

1. Gather the Notes. Messages, timelines and meeting notes from the work.
2. Write the Goal. One sentence, so every lesson is measured against it.
3. List What Happened. Facts only, no reasons yet.
4. Sort Good from Hard. Mark what worked and what got in the way.
5. Ask Why for Each Problem. Look for a gap in a process, not a person.
6. Write One Change. Make it small enough to try.
7. Date and Store It. A log that nobody can find teaches nobody.

A Short Example

An invented entry from a volunteer food drive.

Goal: Collect 500 pounds of food in one Saturday. What happened: Doors opened at 9 am. The first donors arrived at 8:30 and waited in the rain. We collected 410 pounds. What went well: The sorting tables were set up the night before. What got in the way: Nobody was at the door at 8:30. The sign-up sheet showed volunteer shifts starting at 9. Why: The flyer gave no opening time, and no one was scheduled before 9. Change to try: Put the opening time on the flyer and add an 8 am greeter shift to the sign-up sheet. Owner: volunteer lead. Still unknown: How many donors left because of the wait.

Common Mistakes

• Writing Blame. A lesson about a person is not a lesson. Look for the gap in the process.
• Too Many Lessons. Pick the few that matter.
• No Owner for the Change. A change with no owner does not happen.
• Mixing Facts and Reasons. Keep what happened apart from why.
• Filing It Where Nobody Looks. Put it where the next planner will start.

How to Do It with AI Using the Template

The Logic Lab template, "Run a Lessons-Learned Review," takes your notes on a finished project and what it set out to do. It lists what happened, sorts what went well from what got in the way, asks for the cause of each problem, and suggests one change for each.

Checks are built in. The template confirms that each event is quoted from your notes, that no number appears that your notes do not have, and that the output has a line asking you to check it with the people who were there. It asks you to confirm that no person is blamed.

The template runs in your own AI tool. Logic Lab runs no AI and does not see what you paste. Read the finished log yourself before you file it.