"LESSONS LEARNED" DATABASE

A month ago I decided to build a  “lessons learned” database that can be used to continually improve project processes in the company. I searched for some tips to help me prepare the database and that's what I found: 

• Recording Lessons Learned Record both the problem and the solution as well as important project attributes in a single easily accessible database. This makes it easier to identify recurring issues, to update the data and to maintain the accuracy and relevancy of the data.
  
• Categorization
  Ensure that the data are grouped and searchable by key attributes such as project name, type, size, business area, functional area or any other attributes that have meaning for your organization.
  
• Communication
  Inform all project teams whenever the database is updated with new information and, more importantly, raise awareness whenever the data has resulted in a change to the organization’s project processes.
  
• Encourage use of the database
  Allow free and informal access to the pool of knowledge and permit comments and feedback. Invite suggestions for process improvement based on the lessons learned data.
  
• Data Review
  Periodically review the data to remove out-of-date or redundant data to maintain a high level of confidence in the database. It should always be current and accurate.
  
• Continually Improve Processes
  Search for problems that exhibit similar patterns and instigate appropriate process changes such as introducing additional tasks and checks or changing the sequence of certain activities or changing optional tasks to mandatory ones.