Lessons Learned in Project Management

Every project is an opportunity to gain new experiences and provide you with lessons that will be beneficial to future initiatives.

Lessons learned are part of organizational process assets and assist the project management team in improving their processes and skills and avoiding repeating previous mistakes.

In today’s post, I will explain the lessons learned, their importance, and their benefits, and highlight best practices. By examining these lessons learned, you can better navigate challenges, optimize team performance, and deliver projects on time and within budget.

Whether you’re an experienced project manager or new to project management, these insights will enhance your project management acumen.

What Are Lessons Learned in Project Management?

Lessons learned are knowledge gained from previous projects in such a way that it can help future projects. Lessons learned in project management are crucial for improving work performance in future projects.

Lessons learned are collected throughout the project lifecycle and contain all positive and negative events. The goal is to reuse the best practices and avoid the same mistakes in the future.

The PMBOK Guide defines the lessons learned process as a “collection of interconnected actions and activities undertaken to accomplish a specified set of goods, results, or services.”

Lessons learned are knowledge gathered from project experiences, both successes and failures. They capture what worked well, what didn’t, and why. Based on this experience, you can take corrective and preventive actions to improve your workflow in the next projects.

Stages in the Lessons Learned Process

chart showing lessons learned collection process

The lessons-learned process involves five stages:

Identify: Make a list of comments and suggestions. These can be sources of information for future initiatives.
Document: Record all information, discuss it, and highlight the lessons learned during the conversation.
Analyze: Analyze and arrange the lessons learned. They can be used in training or to enhance project-management processes.
Store: Keep a copy of the lessons-learned reports on a shared disk or in the cloud so that they are accessible to all project teams.
Retrieve: You can retrieve the lessons learned from the archive for use in your current project.

Lessons Learned Benefits

A few lessons learned benefits are:

Sharing Knowledge: The lessons learned provide a structured method for collecting and sharing experiences, insights, and expertise within a team or organization. This collective knowledge will ensure that everyone has access to valuable information, thus reducing the learning curve for new team members and improving overall competence.

Avoiding Mistakes: Documenting and reviewing the lessons learned from past projects can help you identify what went wrong and why. This can help prevent you from repeating the same mistakes, thus leading to fewer errors and smoother execution in future projects.

Improving Skills: Analyzing what went well and what didn’t will allow team members to understand their strengths and areas for improvement. This continuous reflection and feedback loop will promote the development of skills and competencies, thus enhancing performance over time.

Optimizing Processes: The lessons learned often highlight inefficiencies or bottlenecks in current processes. By addressing these issues, organizations can streamline workflows, reduce waste, and improve productivity, leading to more efficient, effective processes that save time and resources.

Promoting Professional Growth: Engaging in the process of capturing and applying the lessons learned will promote critical thinking and problem-solving skills. It will also encourage a growth mindset in which team members will be open to learning and adapting. This will contribute to personal and professional development.

Saving Time: Learning from past experiences can help teams avoid redundant efforts and missteps. By applying these insights, you can complete projects with fewer obstacles, thus saving valuable time that can be allocated to other important tasks.

Improving Quality: The lessons learned will provide a feedback mechanism to identify and correct defects or deficiencies in products or services. Implementing these improvements will enhance the quality of deliverables, thus leading to higher customer satisfaction and better outcomes.

Promoting Innovation: Reflecting on the lessons learned can spark new ideas and innovative solutions. Understanding past challenges and successes can inspire creative thinking and encourage the exploration of new approaches, thus driving innovation and keeping the organization competitive.

How to the Capture Lessons Learned

Capturing lessons learned requires a structured process to ensure you get valuable insights from all stakeholders, which are recorded.

Start by planning and preparing for the lessons learned session, defining objectives, and assigning a facilitator. Conduct review sessions at key project milestones with diverse stakeholders to provide comprehensive feedback. To collect data, you can use brainstorming sessions, interviews, surveys, and review project documents, logs, etc.

Facilitate discussions in a non-judgmental environment, focusing on key areas such as successes, challenges, and areas for improvement. Encourage participants to provide specific examples and actionable insights.

Team members can be hesitant to share negative lessons learned, so you must clarify that this exercise is not to express personal rage. You should welcome positive criticism, as the lessons learned exercise is about providing useful and constructive criticism to improve processes and avoid previous errors.

Document lessons learned using standard templates, categorizing them into technical, process, management, and cultural types.

Analyze the collected data to identify trends and patterns, validating the findings with the team.

After completing the lessons learned, you will create a lessons-learned report and share it with stakeholders for their feedback and comments. After receiving their responses, you will update and archive the report in your organizational process assets.

The lessons-learned report includes:

Summary: This is a one-page summary with recommendations.
Executive Report: This is a review of the lessons learned (e.g., what went right or wrong and how you can improve processes).
Findings: This is a summary of the problems discovered.
Recommendations: These are actions to avoid negative events and realize opportunities.

You can email the final report to stakeholders, publish it on the portal, archive it on OPA, and use it during presentations or in a newsletter.

You should document the lessons learned throughout the project lifecycle. Capturing the lessons learned is a continuous process. You should encourage team members to share the lessons learned whenever possible. They should not wait for a specific time; instead, they should record the lesson as soon as they learn it.

The following are a few methods with which to collect and document the lessons learned:

Post-Project Reviews: In a post-project review, you will evaluate what worked and what didn’t. You can have an open conversation about the project and use this knowledge for your next project. After completing the exercise, you will update the record. Ensure the presence of key team members in this exercise and ensure that they share the lessons learned.

One-on-One Meetings: Meet with your key stakeholders and ask about the lessons they have learned. During these meetings, you may discover that some stakeholders are more willing to offer feedback, and you may collect some valuable ideas. Team members may be willing to discuss their accomplishments in a group discussion but may not be willing to admit their mistakes. In a one-on-one meeting, they may be less concerned about others overhearing their faults, so they will speak freely.

Team Meetings: Don’t wait until the project is completed to compile the lessons learned. Make it a regular exercise. Inquire about what team members have learned during the week, discuss it in an open environment, and record it. Although useful lessons may not be learned in every meeting, the process will create an environment in which team members are encouraged to share their experiences.

Wikis/Software: Encourage your PMO to create a wiki for the lessons learned if one does not already exist. Wikis are simple to develop and allow all team members to contribute. Keep the wiki updated throughout the project lifecycle, making it a useful learning resource.

Lunch Sessions: Team meetings are useful with team members, but lunch sessions have a larger audience. You conduct these sessions during lunch and let team members from other projects in your organization join. This can help knowledge-sharing across different teams. Lunch sessions are informal meetings and good knowledge-sharing exercises.

What Should You Include in the Lessons Learned?

What Went Well?: This includes positive experiences. If you don’t look at what went well, you may avoid using strategies to realize opportunities in future projects.

What Did Not Go Well?: This includes negative experiences. Learning from your mistakes is essential. Ignoring what went wrong will ensure that you repeat the same mistake.

Were the Project Milestones Met? If Not, Why?: Project milestones are important project events. If you miss your key milestones, then you should review the causes and ensure that you do not repeat these mistakes in the future.

Best Practices for Documenting the Lessons Learned

Use the following best practices to capture the lessons learned:

Don’t Get Caught Up in Past Mistakes: Don’t obsess over past issues (e.g., as a disagreement with a stakeholder or a task you failed to complete). While this can be reasonable, it is also unproductive. Accept unpleasant experiences and concentrate on learning.

Remember That Stakeholders Will Always Criticize: Even the finest project managers face criticism because projects are constantly debated inside the organization. Remember that many of your colleagues will point out your mistakes, and you may not be appreciated for your hard work.

Be Willing to Learn: Accept that you may not always have the greatest solution. Some project activities can be planned better. You will improve if you are willing to learn.

Lessons Learned Examples

Now, I will provide you with two examples of lessons learned in different formats.

Example #1

Example #2

Project Overview: This was a construction project to build a commercial office complex. The project experienced delays and cost overruns but was ultimately completed successfully. The project manager conducted a lessons-learned session to capture insights for future projects.

Technical Lessons Learned

Issue: Incorrect soil-testing results led to foundation issues, thus causing delays.
Lesson: Ensure that thorough, accurate geotechnical surveys are conducted before the design phase.
Action: Implement a more rigorous soil-testing protocol and involve experienced geotechnical engineers.

Process Lessons Learned

Issue: Inadequate subcontractor scheduling resulted in workflow interruptions.
Lesson: Properly sequence subcontractor activities and improve coordination.
Action: Develop a detailed, realistic project schedule, regularly update it, and maintain close communication with subcontractors to ensure their adherence.

Management Lessons Learned

Issue: Poor communication between project managers and site supervisors led to misunderstandings and errors.
Lesson: Establish clear communication channels and regular update meetings.
Action: Schedule weekly progress meetings and use project-management software to inform all stakeholders.

Summary

Collecting lessons learned in project management is a key process for generating knowledge and passing it on to future generations. By capturing lessons learned, you get valuable insights from successes and challenges. This knowledge allows you to continuously improve, identify areas for optimization, and equip future project teams for greater achievement.

Critical review is vital for effective lessons learned. Build confidence in your team members so they can speak their minds freely. Also, ensure that no one blames other team members for past errors.