Lessons Learned Handbook:
Organization Line Manager
Review the draft lesson learned and send it to the appropriate SME to
validate the technical accuracy of the document, assist with keyword or
functional category designations, confirm priority descriptor, and confirm
applicability to other organizations.
Send the validated document to the organization's director/manager for
approval and release.
Distribute the lesson learned internally to the appropriate organizations within
your site or facility. Distribution methods should be determined by your
organization and may include electronic mail, bulletin boards, or other options.
If the lesson is applicable DOE-wide, format the document in conformance with
the DOE lessons learned template, ensure that a unique identification number
is included in the document, and place on the DOE Lessons Learned
Information Service and, if appropriate, the DOE Lessons Learned List Server.
Each Operations Office should develop a numbering scheme for their lessons learned
that are placed on the DOE Lessons Learned Information Service. The numbering
scheme should be consistent with the description of the Lessons Learned Identifier
provided in the Lessons Learned Technical Standard. This description is as follows:
"a unique identification number to assist in referencing a lesson learned including
calendar year, operations office identifier, organization of field/area office/contractor
identifier, and a sequential number (e,.g., 1995-CH-BNL-0019; 1995-ID-LITCO-0118)."
Although there is no requirement for numbering internal lessons learned, it is
recommended that a numbering system be developed to assist with storing and
accessing lessons learned.
Helpful Tips for Writing a Lesson
Be concise and brief in the description of the lesson and
Include examples which indicate scope of applicability.
Spell out acronyms.
Include contact person for follow-up information.
Obtain classification review prior to entry on any computer system.