Lessons learned template
A lessons learned review asks what happened on a project, why, and what to do differently next time. The questions are below. The board fixes the usual problem with lessons learned: they get written down and never used. Each lesson becomes an action with an owner, and you can see whether it happened.
Free for 3 projects, forever. No credit card.
Weekly demo to the client
Budget tracked every month
Requirements changed after design sign-off
Get sign-off on scope before design starts
Add scope sign-off to the kickoff checklist
New project brief template
The 5 columns
What each one is for. Rename, reorder or add columns whenever the work needs it.
- Went Well
- What worked and should be repeated.
- Didn't Go Well
- What caused delays, rework or stress. Describe the event, not the person.
- Lessons
- What you'd tell the next project team, in one sentence each.
- Actions
- Changes to make so the lesson sticks: a checklist, a template, a rule. Each with an owner.
- Donecounts as done
- Actions that were carried out. Counts as done.
Lessons learned questions
Send these round a few days before the review, so people come with answers.
What happened
- What did we set out to do?
- What actually happened?
- Where were the differences, and why?
What worked
- What went better than expected?
- What would we do the same way again?
- Which tools, habits or people made a difference?
What didn't
- Where did we lose the most time?
- What did we find out too late?
- What would we change if we started again tomorrow?
What's next
- What should the next project team know on day 1?
- What should we change in how we start projects?
- Who will make each change, and by when?
How to run a lessons learned review
-
Step 1
Hold it soon after the project ends
Within 2 weeks, while people remember. For a long project, hold one at each major milestone too.
-
Step 2
Collect before you meet
Share the board and the questions. Everyone adds cards to Went Well and Didn't Go Well on their own before the meeting.
-
Step 3
Look for causes in the meeting
Group similar cards and ask why each happened. Keep asking until you reach something the team could change.
-
Step 4
Write lessons, then actions
Turn each cause into a lesson card, then into an action with an owner and a due date. A lesson with no action is a note, not a change.
-
Step 5
Use it at the next kickoff
Before the next project starts, open the board and read the Lessons column. Search finds archived cards too.
With your AI agents
An agent can prepare the review from the project board: what finished late, which cards moved back, and where work waited, so the meeting starts from facts. It can also add the agreed actions as cards.
Agents connect over MCP or the REST API, on every plan, and act as you.
agentget_board("Website rebuild")
agentcreate_project("Website rebuild: lessons", template: "lessons-learned")
agentcreate_card("Website rebuild: lessons", "Add scope sign-off to the kickoff checklist", column: "Actions")
Keep it working
- Blame stops people talking. Ask what happened and why, never who.
- Lessons that apply to every project belong in your project templates or checklists, where people will meet them.
- Keep one lessons board for all projects and tag each card with the project, so you can search across them.
- Check the Actions column a month later. If nothing moved, the review didn't work.
Questions
About this template
What is a lessons learned template?
A structure for reviewing a finished project: what was planned, what happened, what worked, what didn't, and what to do differently. It's sometimes called a post-project review or a project retrospective.
What's the difference between lessons learned and a retrospective?
They ask similar questions. A retrospective is usually short and regular, at the end of each sprint. A lessons learned review usually looks back on a whole project or phase.
Is this template free?
Yes. It's on the Free plan: 3 projects with unlimited cards, forever. No credit card. Reviewing with your team on one board needs Pro.
Can I export the lessons?
Yes. Every board exports as CSV or JSON, so you can put the lessons in a report or a shared drive.
Other templates
Start from this template
Free for 3 projects, with no credit card to enter. Every board exports as JSON or CSV whenever you want to leave.