Program Administration - std7501990015

DOE-STD-7501-99

processes. Lessons learned should draw on both positive experiences good ideas that prevent

accidents or save money, and negative experiences lessons learned only after an undesirable

outcome has already occurred. They should include the broad base of work effectiveness and not

be limited solely to specific areas such as safety or safeguards. The relationships of lessons

learned and other management information sources should be clear and understood. Lessons

learned should communicate only lessons, and should not duplicate nor replace other

management information functions like self assessment or event investigation and corrective action

systems.

Program Administration

3.2.3

Administration of the lessons learned programs should be transparent to the user community.

Performance measures should focus on how well a lessons learned program uses opportunities to

develop lessons, the quality of the lessons the program creates, and how well business and

operating practices integrate lessons into improvements. The lessons learned infrastructure

should use existing networks (e.g., SELLS), existing databases, and existing delivery systems

where possible. Lessons learned should be part of everyone's job but clearly defined ownership

should be established for maintaining the infrastructure and support for lessons learned

development, communication and use. Local sites should evaluate lessons they develop to

determine if they appear applicable to the wider DOE community. If so, they should be distributed

via the Corporate lessons learned system for consideration at other DOE sites. Lessons may also

come from Headquarters analysis or from non-DOE organizations and sources. Local sites

should evaluate outside lessons for local application and dissemination.

User Community

3.2.4

The user community for the DOE lessons learned program is DOE-HQ personnel, DOE field

personnel and DOE contractor personnel at all levels of the organizations and inclusive of all types

of work performed. Official DOE-wide lessons learned should be available to other government

agencies, industry and the general public.

3.2.5

Information Input

The mechanisms for identifying a potential lesson learned should be simple (in terms of volume,

type of information, and input mechanisms). Lessons should be context driven (information defined

in terms of environment in which learned and significance). The potential types of work or subject

matter should be defined (in terms of information warranting inclusion). There should be no stigma

or blame assigned for individuals identifying a lesson learned.