At a recent PMO FlashMob event, I got chatting with a few FlashMobbers about what can be done with the Lessons identified in project closure reports. There were split opinions in the group:
- Some thought that Lessons are usually specific to the Project concerned, and are only useful in later stages of the same project, or in running future projects that are very similar to the one from which the Lessons were learned;
- Others (including me) thought that it is possible to extract more generic learning from at least some Lessons that can be implemented across many projects (even those that are different from the project that identified the Lesson), perhaps by adding or making a small change to a checklist, template, approach, BAU process or corporate PM methodology, or by including the Lesson in PM training or coaching.
I have written before about Lessons Learned and my ideas on how to use them, but I thought it might be fun to try an experiment, with which I would be grateful for your help.
I have written a web survey containing a number of Lessons learned from projects (some very loosely based on my own experience, and some completely made up) – please take a look at them, and for each one let me know:
- Whether you think it is possible is to draw any learning from the Lesson that can be applied to projects beyond the same type as the original project, and if so
- What learning you would take from that Lesson and how you would apply it.
On completing the survey (which should only take you about 5-10 minutes) you will see a summary of all the coded responses so far (the survey doesn’t allow respondents to see the free text responses). I will also give you the password to a follow-up article outlining my own thoughts on the examples, which I will update periodically with the best quality outputs from the survey.
This idea is explored further in Ken Burrell’s book Learning lessons from projects, available from Amazon.