Free Lessons Learned Template
Start from a filled-in example, then run your own review on the blank template. It compares goals with results, separates what to keep from what to change, and turns every lesson into a recommendation with an owner and a date, so the next project actually uses it.
What is in the pack
- Filled-in example first: an online store reviews its Black Friday peak week
- Blank lessons learned report: goals and results, what went well, what did not, what customers said, lessons, sign-off
- Lessons learned register for every project, with category and status dropdowns; overdue actions turn red
- Review meeting agenda: the four after-action review questions in 90 minutes
- The report as a Word document, plus a printable PDF
Lessons learned example: Black Friday peak week at an online store
Illustrative example, not customer data. This is page 1 of the template; the next pages are the same report, blank.
| Section | Example |
|---|---|
| Project | Peak week, Black Friday to Cyber Monday · Review held 10 days later: 90 minutes, 11 people from e-commerce, logistics, customer service, marketing and IT |
| Goals and results | Orders 14,300 against 12,000 (met) · On-time delivery 81% against 95% (missed) · First reply to tickets 19 hours against under 4 (missed) · CSAT 71% against 85% (missed) · Site uptime 100% (met) |
| What went well | The site stayed up at three times normal traffic, thanks to a load test two weeks before. Orders beat the target by 19%. |
| What did not go well | 2,300 orders waited two to four days for carrier pickup: capacity was booked for the forecast, with no fallback carrier. Support was staffed from order volume, not from last year’s tickets. |
| What customers said | 1,240 tickets in the week (310 in a normal week): delivery delays 46%, items out of stock after ordering 18%, discount code not applied 12% |
| Lesson 1 | Carrier capacity is the bottleneck when orders beat the forecast → book the forecast plus 25% and sign a fallback carrier before the peak. Owner: logistics manager, by 31 Jan. |
| Lesson 2 | Support volume follows tickets, not orders → staff from last year’s peak tickets and add an automatic delivery-status reply. Owner: CX lead, by 15 Feb. |
| Lesson 3 | Keep the load test two weeks before every peak. It worked. |
How to run a lessons learned review in 5 steps
- 1Hold it within two weeks of the end, while people still remember, and invite everyone who did the work.
- 2Start from the goals in the plan and the actual results, with numbers.
- 3Bring what customers said: tickets, reviews and survey comments, grouped by theme.
- 4For each gap, ask why until you reach something in the plan or the process you can change. No blame.
- 5Write each lesson as a recommendation with an owner and a date, put it in the register, and check it before the next project starts.
Lessons learned questions: a 90-minute review agenda
The four after-action review questions, then who does what by when. The same agenda is in the pack.
| Time | Question | What to bring and how to run it |
|---|---|---|
| 5 min | What did we set out to do? | Goals and targets from the plan, not from memory |
| 15 min | What actually happened? | Facts and numbers: results, timeline, tickets, reviews and survey comments by theme |
| 30 min | Why was there a difference? | Causes in the plan or the process, not in people. Ask why until you reach something you can change |
| 25 min | What will we keep, and what will we change? | Each lesson becomes one recommendation with an owner and a date |
| 15 min | Who does what by when? | Read back the actions and agree when to check them |
Related free templates
Frequently asked questions
Is the lessons learned template free?
Yes. The printable PDF downloads without an email. The Excel pack and the Word report are sent to your email for free.
What is a lessons learned report?
A short record, written after a project, launch or event, of what was planned, what happened, why there was a difference, and what the team will do differently. Its output is a list of recommendations with owners and dates, not a story.
What questions do you ask in a lessons learned meeting?
The four after-action review questions: what did we set out to do, what actually happened, why was there a difference, and what will we keep and change. Then agree who does what by when.
When should you hold a lessons learned review?
Within two weeks of the end of a project, launch or event, and at the major milestones of a long project. If you wait until everyone has moved on, the details are lost.
Why do lessons learned get ignored?
Usually because they are written as observations, such as "communication could be better", with no owner. Write each one as an action with an owner and a date, keep them all in one register, and read the register when the next similar project starts.
Is there a Word, Excel or Google Sheets version?
Yes. The pack has an Excel workbook with four sheets (example, blank report, register, review agenda) and a Word version of the report. For Google Sheets, upload the .xlsx file to Google Drive and open it with Google Sheets; the dropdowns and colours carry over.
What if the evidence is thousands of tickets and reviews?
Grouping a week of tickets by hand takes days. Pivony groups all of your tickets, reviews and survey comments by topic and root cause, so a lessons learned review starts from all of them, not a sample.
Want the customer side of every review?
Pivony groups all of your tickets, reviews and survey comments by topic and root cause, so a lessons learned review starts from all of them.
Get a free root cause audit