Some great comments on this Linkedin post. From my perspective the key problem is we are okay at indentifying lessons learned and bad at disseminating lessons back into the organisation. The people factors, organisation and project culture is what will often get in the way. We should be starting a lessons learned log from project day 1 (based on previous projects) and maintain the log throughout the project. …Regards, Stephen
“Lessons learned provide a competitive advantage, I do not see them being shared with third parties via professional association websites”. I would be interested to hear your comments.
From what I have seen, most organisations maintain their lessons learned in house for competitive advantage, although some organisations (mainly government) make their lessons learned available to the public (NASA http://llis.nasa.gov/llis/search/home.jsp, US Department of Transportation http://www.itslessons.its.dot.gov/ )
What organisations do you know have shared their lessons learned?
Looking forward to hearing from you all.
The Draft ‘A Guide to the Project Management Body of Knowledge (PMBOK® Guide) — Fifth Edition’ is currently open for comments. I have made a couple of reccomendations.
1) General comment for ‘lessons learned’. I am interested in understanding why Project Management methodologies and PM knowledge books seem to only use the term ‘lessons learned’? Perhaps the Project Management community needs to shift the focus to more knowledge management, which will open up the language we use in organisations. Lessons learned is only one particular element that can be used to share and use project knowledge. …Your feedback would be most welcome.
2) Section: 188.8.131.52 Organizational Process Assets needs to also include ‘Lessons learned from previous projects’
As I read more over the next few weeks, more feedback will be provided.