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...
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.
Look like a good way to present the lessons learned.
Do you use a predefined template or each make a new one?
...
1 reply by Rami Kaibni
Apr 18, 2017 3:23 AM
Rami Kaibni
...
We use a very general template for the presentation and tailor it deoendign on the type of lesson learned being addressed.
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)
Where they base on template or simple document?
...
1 reply by Mayte Mata Sivera
Apr 17, 2017 4:52 PM
Mayte Mata Sivera
...
From my point of view, templates are better. Like this, all the team members will understand the needs or the desired information that they should document in the lessons learned.
From my point of view, templates are better. Like this, all the team members will understand the needs or the desired information that they should document in the lessons learned. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Apr 17, 2017 4:36 PM
Replying to Vincent Guerard
...
Look like a good way to present the lessons learned.
Do you use a predefined template or each make a new one?
We use a very general template for the presentation and tailor it deoendign on the type of lesson learned being addressed. Saving Changes...
Kaustubh JoshiConsulting Analyst| FreelanceMumbai, Maharashtra, India
My lessons learnt item will contain
1. Description of the lesson learnt (What was done right or wrong, under which circumstances,etc.)
2. Process Group
3. Knowledge Area
4. Supporting attachments
5. Suggestions
Along with other relevant project details.
...
1 reply by Vincent Guerard
Apr 18, 2017 12:43 PM
Vincent Guerard
...
Thanks Kaustubh,
Do you also put the list of participants? So if clarifications a needed they can be contacted.
1. Description of the lesson learnt (What was done right or wrong, under which circumstances,etc.)
2. Process Group
3. Knowledge Area
4. Supporting attachments
5. Suggestions
Along with other relevant project details.
Thanks Kaustubh,
Do you also put the list of participants? So if clarifications a needed they can be contacted. Saving Changes...
Hi all,
I am supportive of template usage for LL and a database storage of them.
One issue that concerns me is how to avoid repetition of same LL.
For small companies it may be easy but in global companies it is more complicated to avoid that lesson 11 is not the same has lesson 123.
What are your suggestions to solve this issue? How to assure that all LL are read when you have a big database?
...
1 reply by Vincent Guerard
Apr 19, 2017 6:49 PM
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?
Saving Changes...
Lisa FunderburgSenior Program/Project Manager| GovernmentBroomfield, Co, United States
Our PMO includes the lessons learned within the project closure/production turnover document. We state the names of those that attended the LL meeting but don't necessarily attribute the idea to a single contributor (in my experience once one idea is given everyone pipes up and agrees on different variations of that idea). We break down our LL into planning, requirements, build, etc. phases and then any pro/cons from it.
...
1 reply by Vincent Guerard
Apr 19, 2017 6:54 PM
Vincent Guerard
...
Thanks,
So your project just get one LL at the closure.
Do I understand that your LL meeting you identify things that need to be improve, and request solutions from participant?
Hi all,
I am supportive of template usage for LL and a database storage of them.
One issue that concerns me is how to avoid repetition of same LL.
For small companies it may be easy but in global companies it is more complicated to avoid that lesson 11 is not the same has lesson 123.
What are your suggestions to solve this issue? How to assure that all LL are read when you have a big database?
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?
...
1 reply by Diego Canas
May 23, 2017 6:24 PM
Diego Canas
...
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.
Our PMO includes the lessons learned within the project closure/production turnover document. We state the names of those that attended the LL meeting but don't necessarily attribute the idea to a single contributor (in my experience once one idea is given everyone pipes up and agrees on different variations of that idea). We break down our LL into planning, requirements, build, etc. phases and then any pro/cons from it.
Thanks,
So your project just get one LL at the closure.
Do I understand that your LL meeting you identify things that need to be improve, and request solutions from participant?
...
1 reply by Lisa Funderburg
Apr 20, 2017 10:09 AM
Lisa Funderburg
...
Not necessarily one LL meeting, that's just one where it lives. For longer projects, we will do them throughout and then collect them into that production turnover document.
It depends on the team and my relationship, most times I give them a prompt and then sit quiet and record. This is their time to really reflect and review- things that need to improve, things that went right, processes to update, things we have control over, things we have no control over, vendor issues, internal/PMO issues, etc. I contribute to keep the conversation rolling. If I need, I can structure it more but I typically don't say "okay, now we're going to review the planning phase. What can you tell me about it", unless the team/conversation is stifled and need more direction.
Community Champion
