Contact ME

Comments? Suggestions? Compliments? I'll take them all.

Please use the form on the right to contact me.

 

 

         

123 Street Avenue, City Town, 99999

(123) 555-6789

email@address.com

 

You can set your address, phone number, email and site description in the settings tab.
Link to read me page with more information.

Why You Should Write a Lessons Learned Report – Template Included

@Work

Eldon Kao
Continuous Improvement Blog

Why You Should Write a Lessons Learned Report – Template Included

Eldon Kao

Six Sigma is a process like any other it is employed to improve. As such, it is also subject for continuous improvement. There are bound to be obstacles and challenges encountered throughout the weeks and months undergoing the DMAIC process. The purpose of documenting Lessons Learned is to catalogue issues in order to better predict and prevent similar incidents in future Six Sigma projects. On the other hand, there are likely many key successes during the project. The Lessons Learned is also a place to note desired results and perhaps develop a strategy to cultivate those behaviours. The effectiveness of the Lessons Learned document is limited only to the lessons recorded, therefore it is important to recognize lessons as they present themselves. The following events should prompt documentation:

Impact to Triple Constraint (Scope, Cost, Schedule)
Anytime an action has an either positive or negative effect on any of the triple constraints, it is a good chance to document lessons learned. Take note of the impact level on the project and what action was performed to address the event.

Unexpected Outcomes
Anytime an action has an unexpected outcome, the event should be logged to make stakeholders aware for future issues of the same type.

Winning Factors
Any win that takes place should prompt documentation. It is equally important to take note of best practices and turn them into system processes.

The Format
The each lesson should include a brief description of the event, what action was performed (good/bad), and what the recommended action is for future events.  The idea is to promote desirable outcomes and restrain undesirable outcomes. In order to ensure follow up on these activities, there should be a program initiated to track completion of these items with ownership.

In Conclusion
The Lessons Learned Report is a great tool not to be overlooked at the end of a project. The items captured here will help shape and refine how future projects are performed. Therefore, remember to be mindful of the audience when disseminating the Lessons Learned Report to include all project members, stakeholders, and even project leaders that were not involved.