Project Management Central
|
Please login or join to subscribe to this thread
Request to reuse this Topics: Business Intelligence, Lessons Learned, PMO, Risk Management, Strategy |
||||||
|
||||||
Vincent - Over the years I’ve seen lessons learned captured in a number of different ways. Like any process, the quality of the lessons learned will depend on the quality of the inputs, but it is equally about the outputs. For it to be successful, the lessons learned is not about producing a beautiful report, it is about implementing concrete improvement actions, and ensuring these actions are done.
At its simplest form, a lesson learned may be a statement with the structure: • If you do….then….will happen Ideally it will have third part to it, describing the context • If you do….and these conditions are present….then ….will happen The same kind of simple logic statements can be found in a well designed Logical framework description of a project design: If these Outputs are delivered, and these Assumptions are correct, then these Outcomes will happen”. While in the Logical Framework this type statement describes a plan, a Lessons Learned statement should describe what actually happened. In its more complex form, a Lesson Learned could be told in the form of a story, which describes the context, what happened there and what were the consequences. Lessons learned told via stories are likely to be remembered, and passed on. Lessons learned may also be summarized in the form of a headline, which seeks to capture the story. ...
1 reply by Vincent Guerard
Apr 16, 2017 10:19 AM
Vincent Guerard
...
Thanks Nasrullah,
I like the idea of making it like a story, more can be understood about the context. Do you have key words so to facilitate search?
Hello everyone.
I agree with Nasrullah Mohammed, the more sensitive the format of lessons learned is, the better. It allows team members not to see this process very complex and to record the lessons learned and on the other hand that people use it. Usually in the format of lessons learned is recorded: 1. Who places the lesson learned 2. That it was done right or wrong 3. In what affect the project 4. And how could we improve on future projects Hope this can help you. Good luck. ...
2 replies by Jose Gonzalez and Vincent Guerard
Apr 16, 2017 10:21 AM
Vincent Guerard
...
Thanks Jose
Would you put the name of all who participate in the lessons learned? Apr 16, 2017 11:05 AM
Jose Gonzalez
...
I usually put only the name of a contact, not everyone. But if the lessons learned session is done at a specific meeting, I leave a meeting record with the name of all the participants.
Apr 16, 2017 2:00 AM
Replying to Nasrullah Mohammed
...
Vincent - Over the years I’ve seen lessons learned captured in a number of different ways. Like any process, the quality of the lessons learned will depend on the quality of the inputs, but it is equally about the outputs. For it to be successful, the lessons learned is not about producing a beautiful report, it is about implementing concrete improvement actions, and ensuring these actions are done.
At its simplest form, a lesson learned may be a statement with the structure: • If you do….then….will happen Ideally it will have third part to it, describing the context • If you do….and these conditions are present….then ….will happen The same kind of simple logic statements can be found in a well designed Logical framework description of a project design: If these Outputs are delivered, and these Assumptions are correct, then these Outcomes will happen”. While in the Logical Framework this type statement describes a plan, a Lessons Learned statement should describe what actually happened. In its more complex form, a Lesson Learned could be told in the form of a story, which describes the context, what happened there and what were the consequences. Lessons learned told via stories are likely to be remembered, and passed on. Lessons learned may also be summarized in the form of a headline, which seeks to capture the story. I like the idea of making it like a story, more can be understood about the context. Do you have key words so to facilitate search? Apr 16, 2017 9:49 AM
Replying to Jose Gonzalez
...
Hello everyone.
I agree with Nasrullah Mohammed, the more sensitive the format of lessons learned is, the better. It allows team members not to see this process very complex and to record the lessons learned and on the other hand that people use it. Usually in the format of lessons learned is recorded: 1. Who places the lesson learned 2. That it was done right or wrong 3. In what affect the project 4. And how could we improve on future projects Hope this can help you. Good luck. Would you put the name of all who participate in the lessons learned? Apr 16, 2017 9:49 AM
Replying to Jose Gonzalez
...
Hello everyone.
I agree with Nasrullah Mohammed, the more sensitive the format of lessons learned is, the better. It allows team members not to see this process very complex and to record the lessons learned and on the other hand that people use it. Usually in the format of lessons learned is recorded: 1. Who places the lesson learned 2. That it was done right or wrong 3. In what affect the project 4. And how could we improve on future projects Hope this can help you. Good luck. ...
2 replies by Jose Gonzalez and Vincent Guerard
Apr 16, 2017 6:39 PM
Vincent Guerard
...
My asking is simple.
When reading the Lessons learned and need some clarification. Sometimes the name is someone who left the company, so more name increase chance to get answers. Apr 16, 2017 9:05 PM
Jose Gonzalez
...
Your point of view is right
I use a matrix template with clarifying needed columns.
Apr 16, 2017 11:05 AM
Replying to Jose Gonzalez
...
I usually put only the name of a contact, not everyone. But if the lessons learned session is done at a specific meeting, I leave a meeting record with the name of all the participants.
When reading the Lessons learned and need some clarification. Sometimes the name is someone who left the company, so more name increase chance to get answers. Apr 16, 2017 11:05 AM
Replying to Jose Gonzalez
...
I usually put only the name of a contact, not everyone. But if the lessons learned session is done at a specific meeting, I leave a meeting record with the name of all the participants.
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. ...
2 replies by Maria Latimore and Vincent Guerard
Apr 17, 2017 4:36 PM
Vincent Guerard
...
Look like a good way to present the lessons learned.
Do you use a predefined template or each make a new one? May 24, 2017 9:42 AM
Maria Latimore
...
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. 
Network:11062
Vincent,
I worked with different Lessons Learned structures, from templated excels files, from word documents at the project level in a share point. All depends on the organizations, PMO, or a number of projects/team members. For example, in a case of manufacturing security issues, I saw power point with pictures, completely different in my IT projects. (as Rami noted before) ...
1 reply by Vincent Guerard
Apr 17, 2017 4:37 PM
Vincent Guerard
...
Where they base on template or simple document?
|
||||||
Please login or join to reply
ADVERTISEMENTS
|
"Laughter is the shortest distance between two people." - Victor Borge |
