All project managers are familiar with the concept of lessons learned. Most people think it is an important aspect of project closure and many project teams and organizations have formal processes and IT-based tools to assist the processes. However, studies show that even when lessons learned activities are routinely conducted, the organization does not learn.
How does an organization learn? Well, it doesn’t. The people in the organization learn or the organization ingests people with knowledge that does not currently exist. Then, what happens with all of the project lessons learned activity output? In the better cases it is nicely codified into an IT system that is searchable for use by future project teams. The challenge is ensuring that the project resources seek out the knowledge that has been gathered and then assimilate it for use on the next project.
Why wouldn’t a project team want to tap into the wealth of information so painstakingly gathered and categorized by their fore-project managers? It’s right there for the taking. I can think of a few reasons off the top of my head:
- No one knows it exists
- People know about it, but don’t have the time or desire to review it
- The information is deemed as not useful
- The information is not codified and searchable
Really, when you want information about a past project what is the first thing you do? Do you log into your knowledge management system and start trolling for useful tidbits? Not usually. Usually you ping someone you know who worked on it. Or someone you know who knows someone who worked on it. Then you engage in some email exchanges or phone conversations and possibly meetings. We tend to think tacit knowledge is the most useful knowledge. The most well documented lessons learned won’t give you the back story that a conversation with a person will give you.
For this reason, people think that communities of practice, blogs and other social venues are the best place to gain project knowledge. If that’s the case then why do companies invest in document storage systems to file all of the information and knowledge? Well, a two-pronged approach is probably the best. Gaining information socially is a good way to learn about what is available and to get personal perspectives. Afterwards it may still be useful to tap into the data that is available. There may be statistics, estimates and other hard facts that can be useful in your project initating and planning activities.
Another lesson that should be gleened from this revelation is that as you as the project manager and team are gathering lessons learned, you cannot omit the social method of disssminating this knowledge. Leverage blogs and have your team members tell their stories about what they learned. Initiate and participate regularly in project management communities of practice. Tweet about the lessons you learn.
We cannot learn unless we understand what we need to know or are in a mental place to accept information. We still need human interaction in order to learn. The tools assist us in our learnings, but they are not the only resources. Think about your knowledge recipients the next time you perform lessons learned activities. How will they know your information exists, how will they find it, how have you helped them?
To follow Lisa on Twitter go to http://twitter.com/EPMSolutions. If you’d like to increase your knowledge about lessons learned and get some how-to tips, check out our Lessons Learned eLearning class that is worth 4 PDUs. www.enterprisepmsolutions.com