Back to Project Delivery
Project Delivery
Professional Services
Updated March 2026

How to Create a Lessons Learned for Professional Services

A structured procedure for capturing, documenting, and disseminating lessons learned throughout the engagement lifecycle to promote continuous improvement and prevent the repetition of mistakes.

Purpose

To build organisational knowledge by systematically capturing both positive and negative experiences from engagements, making them accessible so future engagement teams can benefit from accumulated wisdom.

Scope

Covers the ongoing capture of lessons learned throughout the engagement lifecycle as well as the formal lessons learned session conducted at engagement closure, through to publication in the organisational knowledge base.

Prerequisites

  • Engagement team is committed to candid reflection and knowledge sharing
  • Lessons learned template or repository is available and accessible to the team
  • Management supports the lessons learned process as a learning exercise rather than a blame exercise
Compliance Note

Designed to meet professional indemnity requirements, client confidentiality obligations, and industry body reporting standards.

Step-by-Step Procedure

1

Establish the Lessons Learned Framework

Define how lessons will be captured, categorised, and shared throughout the engagement, and communicate the process to the team at the engagement outset.

  • 1.1Select the lessons learned template or tool that the engagement will use
  • 1.2Define the categories for classifying lessons such as planning, execution, communication, tools, and stakeholder management
  • 1.3Brief the team on the lessons learned process during the engagement kickoff
Project Manager
1 hour
Knowledge Base, Project Management Software
Tips
  • Make it easy for team members to submit lessons at any time through a simple submission form or shared document
2

Capture Lessons Throughout the Engagement

Encourage and collect lessons learned on an ongoing basis as significant events, decisions, or outcomes occur during the engagement.

  • 2.1Prompt team members to document lessons after significant engagement events such as milestone completions, issue resolutions, or process changes
  • 2.2Include a lessons learned agenda item in regular retrospectives and milestone reviews
  • 2.3Log each lesson with a description of the situation, what happened, the impact, and the recommended action for future engagements
All Team Members
Ongoing throughout the project
Knowledge Base, Project Management Software
3

Conduct the Formal Lessons Learned Session

Facilitate a comprehensive lessons learned session at the end of the engagement or major phase, bringing the full team together to reflect on the entire experience.

  • 3.1Schedule the session within two weeks of engagement completion while experiences are still fresh
  • 3.2Prepare by compiling all lessons captured throughout the engagement and relevant engagement performance data
  • 3.3Facilitate a structured discussion covering what went well, what did not go well, and what should be done differently
  • 3.4Capture new lessons that emerge from the group discussion
Project Manager
1-2 hours
Video Conferencing Tool, Collaboration Board
4

Compile and Categorise All Lessons

Consolidate all captured lessons into a single document, remove duplicates, categorise them, and refine the descriptions for clarity and usefulness.

  • 4.1Merge all lessons captured during the engagement and from the formal session into one master document
  • 4.2Remove duplicates and combine related lessons where appropriate
  • 4.3Categorise each lesson and ensure the recommended actions are specific and actionable
Project Manager
1-2 hours
Knowledge Base, Document Management System
5

Review and Validate Lessons

Have the compiled lessons reviewed by the team and relevant stakeholders to ensure accuracy, fairness, and practical value before publication.

  • 5.1Circulate the compiled lessons document to the engagement team for review and comment
  • 5.2Incorporate feedback and corrections from the team review
  • 5.3Remove or anonymise any content that could be perceived as personal criticism rather than process improvement
Project Manager
1 hour
Email, Document Management System
6

Publish to the Organisational Knowledge Base

Publish the finalised lessons learned document to the organisational knowledge base where it can be accessed and searched by future engagement teams.

  • 6.1Upload the document to the knowledge base with appropriate tags for searchability
  • 6.2Notify the engagement management community of the new lessons learned publication
  • 6.3Add cross-references to related engagement documents and previous lessons learned
Project Coordinator
30 minutes
Knowledge Base
7

Integrate Lessons into Organisational Processes

Work with the engagement management office or relevant process owners to incorporate applicable lessons into organisational templates, standards, and training materials.

  • 7.1Identify lessons that have implications for organisational processes, templates, or standards
  • 7.2Submit improvement recommendations to the relevant process owners
  • 7.3Follow up to ensure high-impact lessons are incorporated into updated organisational materials
Project Manager
1-2 hours
Knowledge Base, Email
Tips
  • The most impactful lessons learned are those that result in changes to organisational processes rather than just being documented

Quality Checkpoints

Lessons have been captured throughout the engagement lifecycle, not only at the end
Each lesson includes a clear description of the situation, impact, and specific recommended action
The lessons learned document has been reviewed by the team for accuracy and fairness before publication
Lessons have been published to the organisational knowledge base with appropriate categorisation and tags

Common Mistakes to Avoid

Only capturing lessons at the end of the engagement when many details have been forgotten, missing valuable insights from earlier phases
Documenting lessons as vague observations rather than specific actionable recommendations that future teams can implement
Failing to publish or share the lessons learned document, keeping the knowledge locked within the engagement team
Not integrating significant lessons into organisational processes, allowing the same mistakes to be repeated on future engagements

Expected Outcomes

Lessons Captured Per Project

Average number of documented lessons learned per engagement, indicating the thoroughness of the knowledge capture process

Organisational Process Improvements

Number of lessons learned that result in changes to organisational templates, standards, or training materials within six months of publication

Repeat Issue Reduction

Reduction in the occurrence of previously documented issues on subsequent engagements, measuring whether lessons are being applied in practice

Frequently Asked Questions

Should lessons learned be shared with the client?

Sharing relevant lessons with the client can strengthen the relationship and demonstrate a commitment to continuous improvement. However, be selective about what is shared externally. Focus on process improvements and positive outcomes rather than internal team dynamics or sensitive information.

How many lessons should a typical engagement generate?

There is no fixed number. A small engagement might generate five to ten meaningful lessons while a large complex engagement could produce thirty or more. Focus on quality over quantity. Each lesson should be specific, actionable, and genuinely useful for future teams rather than being a generic observation.

How do we encourage team members to share honest lessons learned?

Create a psychologically safe environment by framing lessons learned as a process improvement exercise, not a performance evaluation. Leadership should model vulnerability by sharing their own lessons. Emphasise that the goal is to help future teams, and never use lessons learned content in performance reviews.

How do we make sure future teams actually use the lessons learned?

Include a lessons learned review step in the engagement kickoff process where the team reviews relevant lessons from similar past engagements. Tag lessons with engagement attributes so they are easy to find. The engagement management office should actively curate and promote the lessons learned library.

What is the difference between lessons learned and the post-engagement review?

The post-engagement review is a broader evaluation of overall engagement performance including metrics, financials, and stakeholder satisfaction. Lessons learned focus specifically on actionable insights and recommendations derived from experience. Lessons learned are often a key output of the post-engagement review process.

Want this customised for YOUR business?

We'll tailor every step to your exact operations, tools, and team structure.