Repeat next time

What worked that the next project should copy?

Weekly 15-minute check-ins with the client sponsor caught scope changes before they reached the backlog.
Pairing each new developer with someone from the original team got them productive in their first week.
We wrote the cutover runbook two weeks early and rehearsed it twice, so go-live took an hour.
Avoid next time

What caught us out that others should watch for?

We assumed the vendor API matched its documentation and lost two weeks when it didn't.
Legal review wasn't in the plan, so the launch slipped while we waited for sign-off.
We estimated before seeing the client's data, and the data was in much worse shape than expected.
Recommendations

What exactly should the next team do differently?

Test every third-party API against a sandbox in the first sprint, before estimates are final.
Add legal and security review to the project plan template with fixed time slots.
Ask for a sample of the client's real data before signing off the estimate.
Who needs to know?

Which teams, roles or documents should these lessons reach?

The team starting the next client rollout in March should get the API and data lessons first.
The PMO should add the legal review slot to the standard project plan.
Sales needs to know that estimates depend on seeing the client's data.

What is a lessons learned meeting?

A lessons learned meeting turns a finished project into advice for the next one: what to repeat, what to avoid, what to recommend and who needs to hear it. Project managers often keep a lessons learned template as a document or spreadsheet that one person fills in at project close. Here, the whole team builds it together in one session, so the lessons come from everyone who did the work and leave in a form someone else can use. The board has four columns. Repeat next time collects the practices, decisions and tools that worked and should be copied. Avoid next time collects what caught the team out, written as a warning another team could act on. Recommendations turns both into specific advice, and Who needs to know? names the teams, roles and documents the lessons have to reach. In TeamRetro, everyone adds ideas privately first, then the team groups them, votes on the lessons that matter most and assigns owners to share them. A project wrap-up or post-mortem looks back at what happened and why. A project lessons learned session looks forward, at the next project, the next team or the next time this kind of work comes up. Run it at the end of a project or phase, or straight after a post-mortem to package its findings for other teams. Export the report when you're done and keep it where the next project team will look before kickoff.

Lessons learned meeting format

Repeat next time

What worked that the next project should copy?

Start with what worked, because these lessons are the easiest to lose. Push past "good teamwork" to the specific practice, decision or tool behind it, and ask what made it work here, so the next team knows when it applies. Each idea should read as an instruction someone else could follow.

Avoid next time

What caught us out that others should watch for?

Look for problems another team is likely to meet as well, not one-off bad luck. Keep the focus on situations and processes, and ask for the early warning sign, what would have told you this was coming. A lesson with a warning sign attached is one the next team can act on.

Recommendations

What exactly should the next team do differently?

Turn the strongest items from the first two columns into advice someone outside the room can follow. A good recommendation names the action, when to take it and who usually does it: "Add a two-day legal review slot to every launch plan" is usable, "involve legal earlier" is not. Use voting to pick the five to ten recommendations worth keeping.

Who needs to know?

Which teams, roles or documents should these lessons reach?

A lesson that stays in this retrospective changes nothing. For each recommendation, name who needs to hear it, such as the next project team, the PMO, another department or new hires, and where it should live, such as a kickoff checklist, a playbook or an onboarding guide. Turn the important ones into actions with an owner and a due date in TeamRetro, so they come up again at your next session.

When to use this retrospective

  • A project or phase has closed and you want its lessons in a form the next project team can pick up and use.
  • A post-mortem or wrap-up retrospective surfaced plenty of problems, and you now need to turn them into advice for other teams.
  • Your organization runs similar projects again and again, such as client implementations, migrations or product launches, and keeps meeting the same problems.
  • A team is about to disband or hand over the work, and what it knows will leave with it unless someone writes it down.
  • Your PMO or delivery lead asks for a lessons learned log at project close, and you want the whole team to contribute to it.

Suggested icebreaker questions

  • What is one piece of advice you'd give someone starting this project tomorrow?
  • Which lesson from a previous project helped you on this one?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Write every lesson for a reader who wasn't there. "Communication was bad" helps nobody, while "Agree one channel for client decisions at kickoff" does.
  • Give Repeat next time as much time as Avoid next time. Lessons about what worked are the easiest to lose, because people rarely ask why something went well.
  • Invite someone from the team that will run the next similar project. Their questions show you which lessons are too vague to use.
  • Write about situations and processes, not people. If the project was tense, use anonymous input so the hard lessons still come out.
  • Vote, then keep the top five to ten lessons. A short list the next team reads is worth more than a long log nobody opens.
  • Leave with an owner for each lesson that matters, plus the place it will be stored, such as a kickoff checklist or a delivery playbook.

Frequently asked questions

What are lessons learned from a project?
They are what a team learns from doing a project: what worked and should be repeated, what went wrong and should be avoided, and the recommendations that follow. They only help once they are recorded and shared, so the next project can act on them.
What are examples of lessons learned?
"Book legal review into the launch plan two weeks before go-live." "Test data migrations on full-size data, not a sample." "Name one owner for client decisions at kickoff." Good lessons learned are specific enough that someone who wasn't on the project could act on them.
What are the 5 steps of lessons learned?
A widely used project management model has five steps: identify, document, analyze, store and retrieve. A lessons learned meeting covers the first three, and the last two depend on keeping the report somewhere the next project team will look before kickoff.
What questions should you ask in a lessons learned meeting?
What should we repeat next time? What should we avoid? What would we recommend to the next team? Who needs to know? This template gives each question its own column, in that order.
What is another way to say "lessons learned"?
Teams also say project retrospective, post-project review, after action review or debrief. The formats overlap: a Project Wrap Up Retrospective reviews the whole project and a Project Post Mortem digs into what went wrong, while a lessons learned meeting picks out what the next team can reuse.
Ready to run this retrospective?Try this retrospective live