We are required to produce a lessons learned document as part of the project closure process. We literally have hundreds and thousands of them. Unfortunately, most subsequent PMs/ projects never read them. As such, we have begun an initiative to consolidate them and "institutionalize" them. Lessons Learned are just "observations". We are aiming to change our culture from a "Lessons Learned" to "Lessons Implemented" one.
...
1 reply by Keith Novak
Mar 11, 2019 1:40 PM
Keith Novak
...
One of the problems I see with lessons learned is that it can be impossible to find relevant ones. It can be a situation where databases of lessons learned can grow so large that they become unusable without a very good search engine to filter them.
Saving Changes...
Eric SimmsSenior Program ManagerBaltimore, Maryland, United States
Lesson Learned documents are highly valuable, if used properly. Steve described the main problem with these documents - most PM simply never read them. Saving Changes...
We are required to produce a lessons learned document as part of the project closure process. We literally have hundreds and thousands of them. Unfortunately, most subsequent PMs/ projects never read them. As such, we have begun an initiative to consolidate them and "institutionalize" them. Lessons Learned are just "observations". We are aiming to change our culture from a "Lessons Learned" to "Lessons Implemented" one.
One of the problems I see with lessons learned is that it can be impossible to find relevant ones. It can be a situation where databases of lessons learned can grow so large that they become unusable without a very good search engine to filter them. Saving Changes...
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
Binu, It is one of the important document. The lessons what we learned will be helpful for other people in the organization. Other people may learn from this document. Saving Changes...
Ashleigh Kennett-SmithICT Project Manager| Australian Red Cross LifebloodAdelaide, South Australia, Australia
In my opinion I believe they are important.
From an organisational perspective regardless of whether they are *always* referred to when planning future similar projects, in my experience they are sometimes referred to. It only takes "saving" one project from making a serious mistake or assisting one project to be better planned, to be worthwhile (valuable). If the organisation you work for is not using or getting value from lesson's learnt then perhaps there's an opportunity to help the organisation become better at project management?
From a personal PM skills perspective the process of documenting the lesson's learnt is also an opportunity understand how you can improve your project management capability. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Just as valuable is what is done with those lessons. Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
As valuable as the paper they are written/printed on. Except if you follow Steve/Andrew advice. Lessons learned needs to be implemented, not documented. By implementing a lesson learned as soon as it is learned you record it for eternity, or until it needs to change again. Way, way too often did I hear that we will circle around at the end and look at what went wrong, only for that wrong to be fixed. There are obviously, as with everything in life, exceptions but they should be just that, exceptions.
My question that is always left unanswered is - if you do not or can not do it now, what the hell makes you think you will be able to do it later? Saving Changes...
"More than any time in history mankind faces a crossroads. One path leads to despair and utter hopelessness, the other to total extinction. Let us pray that we have the wisdom to choose correctly."
