All, another good post on the apm site. Lessons Learned 2.0 – When and how to capture lessons learned. I have just made a few comments, hopefully this may encourage some more feedback
Owain: When and how to capture lessons learned (often known more as Lessons Identified) >>> There are many KM methods one can use…(peer assist, scoping, action learning, after action reviews, CoPs, Project reviews, LL ?, Learning diaries, group brainstorming, knowledge cafe, knowledge jam, retrospect’s, post project reviews, knowledge histories, storytelling, case studies, reflection….the list goes on) and the timing should be from Day 1, then weekly, fortnightly or Monthly at regular meetings…
How and when to share lessons learned > http://www.invictaprojects.com.au/pmlessonslearnedblog/?p=299
Adoption – Issues, motivation and ways to gain adoption>>>These are the tricky ones…this is where culture, social and systems block the process.
patw: >>> Your on the mark with a KM solution… Not quite sure on the KM system front?… however my research to date in the KM space would say KM is broken in many aspects as much as Lessons Learned is broken. On the term ‘lessons Learned’ (I really don’t like this label – can we call it something else?) I do believe we should be looking at replacing the ‘Lessons Learned’ terms in PMBOK and PRINCE 2 etc with KM terms, as there are many other KM methods/ways we can share our learning’s.
james: >>> The behavioral issue you mention is very much from my perspective the social/culture factors that block the process. I too have had an interesting background with best (good) practice, I have seen the best and worst of this approach…in summary many PMs do not want to follow others best practice? . why? We just like repeating the mistakes of others? More on this topic in the months to come on http://www.pmlessonslearned.info