Flori / Templates

Lessons learned template (project retrospective)

By the Flori team · Published 2026-10-29 · Updated 2026-10-29

A lessons learned document records what went well on a project, what went badly, why, and what you will do differently next time. It is written at the end of a project, or after each major phase, while the details are still fresh. Its value is not the document itself but the changes it causes: an updated template, a new checklist item, a different way to quote.

What should a lessons learned document include?

A lessons learned document should include the project summary, results against the original goals, what worked, what did not and why, and specific actions with owners for future projects.

The template

Run it as a 45-minute meeting with everyone who worked on the project, and send the write-up within a few days.

What does a completed lessons learned document look like?

A completed lessons learned document compares results with the original goals, names root causes rather than people, and ends with dated actions that change how the next project runs.

Fieldwork Studio's review of the Northwind Bakery website. Names are invented.

• Project summary: Northwind online ordering, 2 November to 4 December 2026, three people at Fieldwork, $13,800 including one change order.
• Results against goals: launched on 4 December as planned; 38% of cake orders online in the first month against a 50% target by March.
• What worked: weekly 30-minute check-ins with written minutes kept decisions clear; the change order for gift cards was approved within a day.
• What did not work: page copy arrived nine days late; the ordering provider's test account expired mid-build and blocked testing for two days.
• Root causes: the copy deadline was in the statement of work but not on the client's own task list; nobody owned third-party accounts.
• Action: add client-owned tasks with dates to every project, visible to the client. Owner Priya; lives in the website project template.
• Action: add "third-party accounts and expiry dates" to the onboarding checklist. Owner Sam.
• Action: quote two extra days of buffer on projects with a payment integration. Owner Priya; lives in the proposal template.
• Numbers: estimated 112 hours, actual 131 (17% over, mostly content delays).

How do I run a lessons learned session?

Run a lessons learned session within two weeks of the project ending, collect input before the meeting, keep the discussion on causes rather than people, and leave with owned actions.

1. Send three questions beforehand: what went well, what did not, what would you change. People write better answers alone.
2. Start with the numbers. Estimate versus actual takes the guessing out of the discussion.
3. Ask "why" about problems until you reach a cause you control. "The client was late" usually becomes "we never put their deadlines where they would see them".
4. Keep it blameless. Describe what happened, not who failed. People share more when it is safe to.
5. Turn each lesson into a change in a template, checklist or contract, with an owner. A lesson with no change is just a story.
6. Include the client for a short version on larger projects. Their view often differs from yours.

How is a lessons learned review different from a status report?

A status report describes where a live project stands for stakeholders; a lessons learned review looks back at a finished project or phase to improve the next one. Use a project status report during the work and a lessons learned review at the end.

How can I keep lessons learned in Flori?

In Flori, the lessons learned review can live as a doc on the finished project, and each action can update the project templates your next projects start from.

Flori is a CRM with project management for freelancers, agencies and small teams. When you have actually saved estimates and time logs, compare them; the project record does not create missing measurements. An assistant such as Claude or ChatGPT connected to your workspace can summarize the project's saved decisions and delays as a starting draft for the review.

FAQ

When should you do a lessons learned review? Within two weeks of a project ending, and at the end of each major phase on long projects. Later than that and people forget the details.

Who should attend a lessons learned meeting? Everyone who worked on the project, and on larger projects the client's main contact for part of it. Keep it under an hour.

What is the difference between lessons learned and a post-mortem? They are the same idea. "Post-mortem" is more common in software and incident work, often after something went wrong; "lessons learned" and "retrospective" are used for any finished project, good or bad.

How do you make lessons learned actually change anything? Turn each lesson into a specific change to a template, checklist or contract, give it an owner and a date, and check at the start of the next project that the change is in place.

Should the client see the lessons learned document? Share a short version on larger or long-term engagements. It builds trust and often surfaces issues the client never mentioned during the project.