ParrotNotes LogoParrotNotes

Lessons Learned Template

A project, a launch, a big deal or an event just ended. Pick a format, put the board on the shared screen and type the lessons as the team calls them out. Rate the impact, note the root cause, turn the important ones into actions with an owner and a date, then print the report or copy it into the project folder. No sign-up for anyone.

Three formats and when to use each

All three ask what to keep and what to change before the next one. They differ in what they look back on.

  • Project lessons learned

    What went well, what didn't go well and what you'd do differently. The plainest format for the end of a project, a phase or a launch. Group lessons by area or phase (planning, delivery, handover) to see where most of the trouble sat.

  • After action review

    Four questions that compare the plan with what actually happened: what was supposed to happen, what actually happened, why there was a difference, and what to sustain or improve. Good after an event, an incident or a single push where the plan was clear.

  • Sales deal lessons

    For a won or lost deal: what the buyer said, where you lost or saved time, what to repeat and what to change. Run it with the deal team within a week of the decision, while people still remember the details.

After action review template: the four questions

An after action review is short and factual. Start with what was supposed to happen: the goal, the plan and the standard everyone agreed on. Then what actually happened, in order, from the people who were there. Only then ask why there was a difference, looking for causes rather than culprits. Finish with what you will sustain and what you will improve next time.

Keep the first two questions apart from the third. Teams that jump straight to "why" argue about facts nobody has agreed on yet. Choose After action review on the board above and each question gets its own lane.

How to run a 60-minute lessons learned session

A suggested plan for a team of four to ten. Change the minutes to fit the size of the project.

  1. Set the frame (5 minutes): say what you are reviewing, that the point is the next project and not blame, and how the report will be used.
  2. Collect lessons (20 minutes): go lane by lane; people call out what they saw and the facilitator types it in. One lesson per card, in plain words.
  3. Group (10 minutes): add areas or phases and pick one on each lesson, so repeated problems show up together.
  4. Prioritise (10 minutes): rate the impact of each lesson and let everyone spend their dot votes, then sort by impact and votes.
  5. Agree actions (15 minutes): turn the top lessons into one to five actions, each with an owner and a due date, and note the root cause where you found it.
  6. Print the report or copy it into the project folder, and send it to whoever runs the next similar project.

Lessons learned vs. retrospective

A retrospective is a recurring team meeting: every sprint, every month, every quarter, with the same people looking at the last few weeks. A lessons learned session closes something that will not repeat in the same form: a project, a deal, an event, a rollout. It usually involves a wider group, asks for root causes and impact, and writes a report for people who were not in the room. For a recurring team retro, use the Retrospective Template.

Lessons learned for sales teams

Sales teams lose most of their lessons between deals. Run the Sales deal lessons format after every large win or loss, and after a trade show or a territory launch with the project format. Look for patterns across sessions: the same stall in procurement, the same missing stakeholder, the same proof the buyer asked for.

The buyer's own words are the most useful lesson. If you also run win-loss interviews, put what the buyer said in the first lane and keep your team's opinions in the others.

Related reading: win-loss analysis, retrospective meeting, sales QBR.

The reason behind each lesson is in the conversation.

A card says "handover to delivery was late"; the ten minutes of talk behind it say why and what to change. Record the review with ParrotNotes and get the summary and action items, so the lessons and owners in the report match what the team said. Free for 100 minutes of recording a month.

Get ParrotNotes free

Related tools

Lessons learned questions