How to Implement a Lessons Learned Approach That Works

So, the project is at an end and you have assembledInside each tab are the following headings
the Team to review what went well and what went- ID Number - Assign each row a unique ID
not so well. Stop! Why have you waited until the end- Description of issue or situation - Describe the issue
to capture something as crucial as the Lessonsor situation leading up the the lesson learned
Learned? Do you really think that the Team will- Team response - What was the response of the
remember everything they should at this stage letTeam? How did they handle and overcome the
alone be motivated enough to impart this knowledge?problem?
Furthermore, it may be difficult to assemble the Team- Resolution or Outcome - What was the eventual
at the end of a project as they may have beenoutcome?
seconded to a new project.- Lesson Learned - State how could this issue be
Lessons Learned are one of the most overlookedavoided next time around
aspects of Project Management. This can be for a- Further Comments
number of reasons including:It is the responsibility of the Project Manager to ensure
- Lack of timethe Lessons Learned are captured during the life of
- No suitable infrastructure to store the Lessonsthe project whilst the information is still fresh in the mind
- No clear processes in place to capture the Lessonsof the Team Members. Doing this ensures most if not
- Lack of resourceall of the lessons are captured ensuring maximum
As a Project Manager I make it known from thevalue is added to future projects moving forward.
outset that I expect Lessons Learned to be capturedStoring Lessons Learned for use buy others
as we move through the project. This is essential asObviously storing this information in a spreadsheet is
the most accurate information can only ever befine for everyday use by the Project Manager but it
garnered at the time of the event.would be a nightmare for future PM's to search
What to capture and how to capture itthrough every spreadsheet from every project the
The following is a comprehensive list of what shouldorganisation has undertaken.Remember also that
be tracked and monitored. For smaller projects this willcommunication is key here. In order to gain the most
be overkill so simply choose what is critical and ignorefrom this you must be talking with your Team at every
the rest.opportunity. Keep them involved, solve the issues and
- Risks / Issuesproblems that arise together and document your
- Change Requestsfindings.
- Supplier issuesThat is why upon completion of the project I advise
- Any quality defectsimporting the various tabs of the spreadsheet into a
- Stakeholder identification and managementSQL or Oracle relational database. If you are not
- Scope managementfamiliar with relational databases then your IT
- Risk identification and managementAdministrator can set one up for you. Suffice to say
- Requirements managementhowever that it is not that hard and allows the
- Schedule development and managementinformation be accessed quite easily. Indeed, you could
- Resource allocationhave your IT Department front end the database with
- Communication managementa nice web interface and make it available on the
- Cost estimating and budget controlcompany intranet. Remember that the more easily
- Quality planning and managementpeople can access this information and find what they
- Change management processare looking for, the more likely it will be used. This has
- Teamwork/team performancehuge consequences for the success of your
- Problem solving/issue resolution processesorganisation's future projects and perhaps for the
- Conflict Resolutionorganisation itself.
Each topic is allocated a tab on an excel spreadsheet.