Project Management

Please login or join to subscribe to this thread

Lessons Learned Archieve

linkedin twitter facebook  
avatar
Manavasi Ramesh PM II| Powergrid Corporation of India Mumbai, Maharastra. India, India
In any project creating Lessons Learned archive is a more important aspect as it helps in addressing the problems in project execution . Most of the time team members are reluctant to post the problems they have faced and how it is resolved. Even any mistakes happened same is to be posted as it helps in finding solutions to avoid such mistakes in future projects . Most of the time team members felt that that it will show them in poor light if the mistakes are noticed by others. and impact their growth in the Organization . Rather it is other way around that this help the other members to address the issues and find out ways to rectify the same in new projects . Do you agree ?
Sort By:
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
In my opinion the problem with this approach is it is focused on problems. You have to focus them as best preactices. In this way, everything will work.
avatar
Abolfazl Yousefi Darestani Manager, Quality and Continuous Improvement| Hörmann-TNR Industrial Doors Newmarket, Ontario, Canada
I agree with Sergio.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Manavasi -

Part of the reason there is this negative connotation is if you hold such sessions infrequently or worse at the end of a project then people tends to focus on what went either really well or really poorly.

This is why a more frequent feedback loop is needed - whether you call them retrospectives or not.

This also needs to be combined with leadership commitment to creating a safe environment where people can express their views without worrying about being criticized for being negative.

Kiron
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
Lessons Learned should be about more than just what went wrong. They should also be about what went right, and if anybody should be recognized for outstanding performance.

In addition to an archive, maintain an action log. If you're holding lessons learned at the end of each project phase, or retrospectives at the end of each sprint, keep track of anything that will require future action on your project. Notify other project managers if something comes to light that will help on other projects.

I agree that it is important for the team to be able to call out mistakes, with an emphasis on how to avoid them instead of on blame, but your meetings will be more productive if you focus on more than just what went wrong and if you take an action-oriented approach, instead of just adding to the archive that nobody reads..

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Common sense is the collection of prejudices acquired by age 18."

- Albert Einstein

ADVERTISEMENT

Sponsors