Download a free Lessons Learned Template in Excel to capture what went well, what went wrong, what warning signs appeared, and what action should be taken before the next project starts.

This template is designed for project managers who need more than a simple end-of-project notes sheet. It gives you a working lessons learned log with example entries, owners, actions, WBS links and status tracking so lessons can be reviewed during the project and reused on future projects.

During a project, the team should document the lessons they have learned, whether positive or negative. For example, a task may have taken longer than estimated, or a new process may have reduced costs.

stakeholdermap.com

The completed log helps other project teams learn from experience and can be added to an organisation-wide project knowledge base.

Lessons learned template capturing project insights, issues, and recommendations to improve future performance

Start capturing lessons that actually improve your next project Download the free Lessons Learned Template (Excel & PDF)

What is included in the lessons learned template?

What is a lessons learned log?

A lessons learned log is a project document used to record useful experience from a project. It captures what happened, what warning signs were visible, what should be repeated, what should be avoided, and what action is needed to improve future projects.

Examples - four real world lessons learned

When to Use a Lessons Learned Log

A lessons learned log is a simple but powerful tool that helps project teams capture experience and improve future delivery. Knowing when to use it will help you get the most value without adding unnecessary admin.

Use this template when:

1. The project runs over several weeks or months

Longer projects generate more insight, both positive and negative. A lessons learned log helps you capture these insights as the project progresses rather than relying on memory at the end.

2. Multiple stakeholders or teams are involved

Projects with different departments, suppliers, or stakeholders often experience communication challenges and coordination issues. Capturing lessons helps improve collaboration on future projects.

3. You want to improve future projects

If your organisation runs similar projects repeatedly, a lessons learned log becomes extremely valuable. It allows you to build a knowledge base and avoid repeating the same mistakes.

4. A formal review is required

Many project methodologies, such as PRINCE2 or PMBOK, require lessons learned or post-project reviews. Using this template ensures you are capturing the right level of detail throughout the project.

5. The project involves risk, change, or uncertainty

Projects that include new systems, processes, or ways of working are more likely to generate useful lessons. Capturing these helps reduce risk in future initiatives.

Practical tip: keep lessons visible during the project

A common problem is that lessons learned are captured but rarely reviewed. One simple way to avoid this is to include your lessons learned log as a tab within your main project status workbook.

By doing this:

• The log sits alongside your regular reporting documents
• It is easier to update during weekly status reviews
• The team is more likely to refer back to it during the project
• Lessons can be discussed and acted on in real time, not just at the end

This small change turns the lessons learned log from a static document into a working tool that actively improves project delivery.

How to Use the Lessons Learned Template (Step-by-Step)

This template is most effective when it is used throughout the project, not just at the end. Follow these steps to capture useful lessons and make sure they improve future projects.

Step 1: Capture lessons as they happen

Do not wait until project closure. Add lessons regularly during the project, for example:

• During weekly project meetings
• After key milestones or deliverables
• At the end of workshops or testing phases

This ensures detail is accurate and smaller but important lessons are not lost.

Step 2: Clearly describe what happened

Write a concise but specific description of the event. Include:

• What happened
• When it happened
• The impact on the project (time, cost, quality, or scope)

Avoid vague statements. The clearer the description, the more useful the lesson will be.

Step 3: Identify whether the lesson is positive or negative

Not all lessons are problems. Mark each entry as:

• Positive – something that worked well and should be repeated
• Negative – something that caused an issue and should be avoided

This helps future teams understand what to replicate as well as what to fix.

Step 4: Record early warning signs

Think about what could have been spotted earlier. Ask:

“What signals were there before this happened?”

This step is often missed, but it is one of the most valuable because it helps prevent issues in future projects.

Step 5: Add clear recommendations and actions

Each lesson should lead to an improvement. Record:

• A recommendation for future projects
• Specific actions to implement the improvement

Focus on practical changes such as updating templates, checklists, or processes.

Step 6: Assign an owner

Every action should have a named owner responsible for taking it forward. Without ownership, lessons are unlikely to be applied.

Step 7: Track status

Update the status of each lesson (for example: open, in progress, closed). This helps ensure actions are followed through and not forgotten.

Step 8: Review and reuse the lessons

Before starting a new project, review previous lessons learned. Use them to:

• Improve planning and estimates
• Update project documentation
• Brief the project team on known risks and good practices

Used consistently, this template helps teams avoid repeating mistakes and build on what works well, leading to better project outcomes over time.

What makes a good lesson learned entry?

A good lesson learned entry is specific, reusable and linked to action. It should help a future project manager understand what happened and what to do differently.

• Specific: explain the real event, not a generic problem such as “communication was poor”.
• Actionable: include a recommendation and a practical action.
• Owned: assign someone to update the process, checklist, template or guidance.
• Reusable: write it so another project team can understand and apply it.
• Balanced: include positive lessons as well as problems.

Common Mistakes When Using a Lessons Learned Log

A lessons learned log can be one of the most useful project documents you create, but only if it is used properly. Many teams complete one at the end of a project and then never refer to it again. To get real value from the template, avoid these common mistakes.

1. Waiting until the end of the project

One of the biggest mistakes is leaving lessons learned until project closure. By then, important detail has been forgotten and smaller issues that could have helped future projects are missed. It is far better to update the log throughout the project, for example at milestones, after workshops, or during regular team reviews.

2. Only recording negative lessons

Lessons learned are not just about what went wrong. Many of the most useful lessons come from things that worked well and should be repeated. For example, a new review process, a better way of running meetings, or an early testing approach that reduced rework. Recording positive lessons helps good practice spread across future projects.

3. Writing vague or generic entries

A lesson such as “communication could have been better” is too vague to be useful. A good lesson should clearly explain what happened, what the impact was, and what should be done differently next time. Specific entries are much more valuable because other teams can actually act on them.

4. Missing the early warning signs

Many teams write down the issue but fail to capture the signs that appeared before the problem happened. This means future teams may still miss the same issue. Including early warning signs makes the log more practical because it helps project managers spot problems sooner next time.

5. Not assigning an owner or action

If there is no clear owner and no action, the lesson is unlikely to lead to any change. A lessons learned log should not just be a record of past events. It should help improve future delivery. Assigning an owner and defining the next step makes it much more likely that the lesson will be applied.

6. Treating it as a document nobody uses

Another common mistake is creating the log simply because project methodology says it should exist. If the document is filed away and never reviewed, it has little value. The best approach is to use lessons learned when planning new projects, updating checklists, improving templates, and briefing teams at project start-up.

7. Failing to link lessons to project work

Lessons are more useful when they are linked to a deliverable, work package, task, or WBS ID. This provides context and makes it easier to understand where the issue or success occurred. Without that context, lessons can become disconnected from real project activity and harder to reuse.

Used well, a lessons learned log helps teams avoid repeating mistakes and build on what worked. The most effective logs are updated regularly, written clearly, and reviewed before the next project begins.

Frequently asked questions

When should lessons learned be captured?

Lessons should be captured throughout the project, especially after milestones, testing phases, workshops, incidents and major decisions. Waiting until project closure often means important detail is forgotten.

What should a lessons learned template include?

A useful lessons learned template should include the event, whether the lesson was positive or negative, early warning signs, recommendations, actions, owner, related work package or WBS ID, and status.

Are lessons learned only for things that went wrong?

No. Positive lessons are just as important because they help future teams repeat what worked well.

Who owns the lessons learned log?

The project manager usually maintains the log, but individual improvement actions should be assigned to the person or team best placed to make the change.

How do you stop lessons learned being forgotten?

Review the log during the project, assign actions, update templates or checklists, and review previous lessons before starting a similar project.

Lessons Learned Log Download

Related project templates