Quality Improvement Zone

A lessons learned log records what happened, what was learned and how that learning could inform current and future improvement work.

Improvement work generates valuable learning from successes, challenges, testing, adaptations and unexpected results. A lessons learned log provides a structured way to capture this learning so it can be reviewed, applied and shared with others.

A lessons learned log should be treated as a living document that is updated regularly as learning emerges. Its value comes not only from recording learning, but from using that learning to improve current and future work.

Improvement projects often generate important insights that can be forgotten if they are not recorded and reviewed. A lessons learned log helps teams capture these insights in a structured way and use them to inform future decisions.

Using a lessons learned log can help you:

• capture learning as it emerges throughout a project
• identify what worked well and why
• understand challenges, barriers and unexpected findings
• avoid repeating approaches that proved ineffective in a particular context
• support continuous reflection and improvement
• share insights with other teams and future projects
• build organisational knowledge and learning

Lessons do not only come from problems or challenges. Valuable learning can also come from successful approaches, unexpected results, adaptations made during testing and assumptions that proved incorrect.

1. Agree how learning will be captured

At the start of the project, decide how lessons will be recorded, reviewed and shared. Establish a simple and consistent approach that works for the team.

2. Assign an owner

Nominate a person to maintain the log and ensure it is updated regularly. All team members should contribute, but a named owner helps ensure the log remains current.

3. Record learning as it emerges

Do not wait until the end of the project. Capture learning throughout the project. Recording learning close to the event helps preserve important detail and context.

4. Describe the context and evidence

When recording a lesson, include enough information for others to understand:

• what happened
• where it happened
• what evidence supported the learning
• why it was important

This helps others understand how applicable the learning might be to their own work.

5. Agree on actions or recommendations

Discuss how the learning should influence future work.

Consider:

• What should continue?
• What should change?
• What should be tested differently next time?
• What should be shared with others?

6. Review and apply learning regularly

A lessons learned log is not only a record for future projects. Teams should regularly review the log and apply relevant learning to the current project.

Use the log to:

• adapt plans
• refine testing approaches
• improve stakeholder engagement
• address risks and barriers

7. Gather different perspectives

Encourage learning to be captured from:

• project team members
• stakeholders
• partner organisations
• people using services
• patients, learners or communities affected by the improvement

Different perspectives may reveal learning that would otherwise be overlooked.

8. Share learning appropriately

Share relevant learning through:

• project reports
• case studies
• presentations
• communities of practice
• future improvement projects

Lessons from one project may need to be adapted to reflect the context, people and system in which they are applied.

9. Complete a final review

At project closure, review the lessons learned log and identify the most important learning from the project. Consider which lessons should be shared more widely and how they may influence future work.