Lesson sharing importance

Another important consideration is how your readers might feel about the subject. Will they be interested in it If not, what can you do to arouse their interest If you ve taken a position on an issue, how likely is it that your readers will share your opinion If they re likely to disagree, how can you help them accept, or at least understand, your position (You ll learn more about this issue in Lesson 11.)... 

The following references provide information on techniques for sharing of lessons learned as well as additional information on some of the case studies that were highlighted in this chapter. Other significant incidents are also cross-referenced in some of these documents. It is important to recognize that some of these publications have heen written from a nontechnical perspective and may not have recognized the concepts or methods covered in this text. 

Ask a few students to share what they wrote in the What I Think It Is and Why I Think So sections of Record Sheet 13-A. If students support their conclusions with a negative result (for example, "it did not bubble with vinegar ), you may want to discuss the idea that negative results can be as important as positive results. (Students will explore the concept of negative results in Lesson 14.)... 

Effort by the CMA will be needed to detect and overcome some natural, negative tendencies inherent in the site-focused management approach. It may even be necessary to limit site manager independence in selecting replacement equipment and software to ensure maximum interoperability. It is important that ECPs be shared between sites so that problems that could well affect more than one site need be solved only once and in a coordinated manner. Evidence shows that this objective has been recognized and appropriate action taken to maximize sharing under the mandatory lessons learned program. ... 

We have lessons to learn from the serendipitous and entirely unanticipated discovery of Cgo. This advance, which opened up a whole new field of chemistry, was the unexpected result of studies in fundamental science. Yet new types of polymers, materials that conduct electricity or store energy from sunlight, fascinating structures with metals or other atoms (even helium) trapped inside carbon clusters, new catalysts, new probes for electron microscopy, and even pharmaceuticals—all of these and other commercial possibilities not yet imagined—are emerging from this exciting discovery. The Cgg story illustrates once more why it is so important, in a technological world, to support research in the fundamental sciences. Where the research will lead cannot be predicted with certainty, but experience shows that the eventual practical benefits that follow, even from only a small fraction of fundamental discoveries, compensate many times over for the initial investment. (Richard E. Smalley, Robert F. Curl, and Harold Kroto shared the 1 996 Nobel Prize in chemistry for their discovery of fullerenes.)... 

We evaluate our architecture in the context of a BMD demonstration. In November 2009, MIT Lincoln Laboratory demonstrated a proof-of-concept net-centric BMD decision-support system during the simulation of an intercontinental ballistic missile (ICBM) attack [10]. For this exercise, we developed and deployed an illustration-of-concept implementation of om siu vivability architecture. This exercise demonstrated the principles of om siu vivability architecture in a realistic simulation of a coordinated ICBM and cyber attack. Our experience developing this survivabihty architecture taught us several important lessons learned, which we share in this paper. 

Sharing best practice across industry sectors, and learning and implementing lessons from relevant incidents in other organisations, are important to maintain the currency of corporate knowledge and competence. 

I would like to broaden the discussion and share with you the Most Important Lessons You Didn t Learn in Engineering School, lessons I have learned during my 35 years in engineering and engineraing management. Some of the lessons were easy to learn otheais were brutally painful. Some of you may have your own lists. As current and future leaders, I hope you learn from the mistakes of others and apply the lessons learned in your own careers. 

Learn from mistakes, your own and those made by others. Don t repeat either. When there is a failure, anomaly, or out-of-family condition, it s important to follow a process. First, find the root cause. Second, develop and implement corrective action. Third, share the lessons learned. Fourth, revise processes to prevent repeating the mistake. 

Accordingly, each project or a sampling of an organization s projects, ranging from the successful to the mediocre or failed projects, should be immediately followed by a post-mortem analysis to determine what can be learned for the benefit of near-future projects. Lessons learned should be documented and widely shared within the organization. Two important components of this post-project review are input from the client, owner or customer and a meeting of the project team. The client, owner, or customer interaction should precede the team meeting so that the team has the benefit of input form those who were served. 

This simple awareness booster—"What have you done for safety "—helps teach an important lesson. Employees learn that safety is not only loss control, an attempt to avoid failure, but can be discussed in the same terms of achievement as productivity, quality, and profits. As a measurement tool, it is possible to count and monitor the number of safety shares offered per meeting as an estimate of proactive safety success in the work culture. 

Another important facet of the reform was the creation of the afteraction review, hi both training and wartime, each significant action is reviewed with the objective of finding lessons to be learned. This is an opportunity for subordinates to share information with senior officers that may be critical of the performance of the unit and of these senior officers. Officers who are resistant to this feedback have difficulty with promotion. 

Lessons learned. Every project is an opportunity to apply PtD concepts to eliminating, reducing, or controlling safety hazards. Every project is also an opportunity to identify additional safe measures and/or lessons learned, although some of those lessons may not be understood until workers have worked in the facility for a while. However, it is important for an organization to not only make necessary safety corrections, but to have a system in place to capture those lessons learned so that the information can be shared and considered during future project design. 

---