Lessons learned to be accessible need to be well structure. Do you have define way to do it (template) or should it be just plain text. Saving Changes...
Diego CanasProject Coordinator | Civil Engineer | Planning Engineer| -Recife, Pernambuco, Brazil
Apr 19, 2017 6:49 PM
Replying to Vincent Guerard
...
Hi Diogo,
Thanks for participating in the discussion
First I rather have two similar LL, has oppose to none. Will they really be identical. Could they bring different solutions?
Use of predefine keywords can reduce the occurence of similar LL.
That brings an other question. You find a LL, use the knowledge found. You have found a new way, so do a new LL or you update the old one?
Hello Vincent!
Answering your last question. I would update the lesson learned by keeping the old text together with the date and would add the new way with the current date. I think it would be easier when you do a search. Except it's a totally different project. In case it would make a new lesson learned.
Thank you! Saving Changes...
Diego CanasProject Coordinator | Civil Engineer | Planning Engineer| -Recife, Pernambuco, Brazil
Hello Vincent,
The lessons learned are structured in an Excel file as follows:
- Project name;
- Date of registration;
- Knowledge area;
- Responsible / Author for registration;
- Description of the cause or reason;
- Description of the solution.
Lessons learned are filled as they occur and in team meeting.
Thank you!
...
1 reply by Vincent Guerard
Mar 31, 2018 9:46 PM
Vincent Guerard
...
Diego,
I like the progressive approach.
Are the spreadsheet document available to all company personal?
Saving Changes...
Maria LatimoreFounder and Principal Consultant| Maria Latimore GroupHyde Park, Ma, United States
Apr 17, 2017 4:54 AM
Replying to Rami Kaibni
...
Hi Vincent,
We do have an online portal where wecstore all our data. One of those sections is dedicated for Lessons Learned and is accessible by all employees. Most of the time we do those on powerpoint as they contain pictures and requires explanation.
Hi Vincent and Rami,
One of my clients also has a data repository where physical versions of lessons learned and all other project documents are stored. This repository is used extensively throughout the organization for people to research and know who's completed what projects. They reach out to those who've completed similar projects to benefit from their experience.
This organization uses a closing report to capture lessons learned, operational hand-offs, etc. I love the idea of capturing stories in the closing document, and will see how it can be revised to add them. Saving Changes...
I agree with the comment that it depends on the organisation.
However, if lesson learn is to be gathered from the inception till the end of the project.
Then the report can be structured to include project management knowledge areas as it applies to the specific project that is being reported.
...
1 reply by Vincent Guerard
Mar 31, 2018 9:47 PM
Vincent Guerard
...
Oluseyi,
What kind of organization don't want the benefits of LL?
Saving Changes...
Lisa RosenblumPMO Communications| Washington River Protection SolutionsWa, United States
I am getting started on a Project Management Lessons Learned program for my company. We currently use a system that is mandated by the government but it mostly relates to big picture practices like safety, systems, and contractor oversight. The system is used by multiple companies. We don't have anything that relates to the management of a project specifically. So when similar projects are performed there is no relatable information. Do you know of any templates or any program information I could reference to help me get started?
...
1 reply by Vincent Guerard
Mar 31, 2018 9:50 PM
Vincent Guerard
...
Lisa,
There are many nice suggestion in this discussion that should inspire you.
LL should be consulted at the initiation of proposal, so they need to be available and practical.
Saving Changes...
Cindy SheltonDputy Director, Project Management| Department of DefenseStafford, Va, United States
Vincent - The least complex method to capture your lessons learned is to reflect practices current in your organization.
If you have a highly visual organization using low technology information radiators - your opportunities should be in that format and captured equally visually and low tech. I like to set aside a highly accessible area where these postits/pictures/notes are captured and reviewed prior to the start of each project or iteration. Kinda fun.
If your organization isn't visual in this way and captures data ostensibly for analysis - it must be accessible in the same location as other project data and tagged with metadata. The medium application is not important with tagged data and will allow future analysis. It may require prior thought on what that meta data will be so you don't have to use sophisticated or costly data mining tools to differentiate between "Costing" and "budgeting" as an example. What ever you do - absolutely weigh the use of the data for the future and the cost of using that data in the future. No point in making it complicated!
...
1 reply by Vincent Guerard
Mar 31, 2018 9:52 PM
Vincent Guerard
...
Cindy,
You are right, if LL are complicated they are not done. Also if information is complicate to access same result.
Product Operations Program ManagerBarcelona, Cataluña, Spain
I currently use Share Point to introduce lessons learned. Several different columns may be added - customized to fit your needs. I find this solution more convenient that excel files stored in a shared drive.
It also contributes in providing an environment for all team members and their lessons learned. Lessons learned are meant to be revisited during project life cycle but also before or during inititating another (similar) project, thus it is important that the information is readily available and easy to find.
We record lessons learnt in excel by knowledge areas Integration, scope, time etc. Each knowledge area has the three famous questions: What went well? What went wrong? and What can be improved or done in a different way? But than we have a column for adding any other details applicable. This exercise is done in an interactive session.
...
1 reply by Vincent Guerard
Mar 31, 2018 9:55 PM
Vincent Guerard
...
Najam,
What is the frequency of those session?
Saving Changes...
ANTONIO REGIOProject Controls Manager| ENDEC Inc.Rizal, Philippines
Normally, Lessons Learned is submitted during every project handover. In our case, lessons learned are collated from weekly and monthly risk and opportunities reports. From this tabled format issues are identified, mitigation required, dates when identified, dates when mitigated, responsible staff (position). Added comments for each item shows each item's impact on time, cost, quality, safety, etc. I like what Rami suggested about adding pictures.
Community Champion
