Today marks the posting of number 400 on this site as well as it’s 10th anniversary! Started in May 2009, lots of updates, news and information over the years and more to come.
In a recently read article this sums up what I try to do each week and over the years:
“The best way to ensure that a lessons-learned document doesn’t just collect dust after being created is by ensuring that it is of quality and that everyone sees its value.
- Collecting and reviewing lessons learned is an ongoing process, not reserved to a particular phase of the project.
- It is a team effort in which each person captures information that they deem useful for future efforts and provides feedback on priorities.
- It is a strategic effort. When I was less experienced, I thought I needed to capture everything, but now I prioritize based on project goals and risks. It is the 80/20 rule, 80 percent of the ROI comes from 20 percent of your lessons learned.
- When populating your lessons-learned template or discussing items, tell stories and use case studies, especially if you are not good at storytelling. There is a gap between intellectually grasping facts and knowing how to apply them. Stories and case studies provide the specifics and context that best practices fail to communicate.”