A Lessons Learned (LL) is knowledge or understanding gained by experience. The experience may be positive, as in a successful test or mission, or negative, as in a mishap or failure. A lesson must be significant in that it has a real or assumed impact on operations; valid in that is factually and technically correct; and applicable in that it identifies a specific design, process, or decision that reduces or eliminates the potential for failures and mishaps, or reinforces a positive result. Proved and validated Lessons Learned to be updated to the company plan and procedure.
Getting big mining projects right: Lessons from (and for) the industry: By Mark Kuvshinikov, Piotr Pikul, and Robert Samek
More than four out of five mining projects come in late and over budget, by an average of 43 percent. One reason for the poor performance is that project leaders find it difficult to know whether and when to intervene. Although they almost always understand when a project is getting into trouble, they may hesitate to make changes because they hope that things will improve or worry that intervention will backfire—what if people get angry or feel too pressured and quit? These are legitimate concerns. In our experience, however, the biggest regret of leaders whose projects went wrong is that they waited too long to act and didn’t go far enough when they had a chance.
Lessons learned in commercial scale-up of new chemical processes (Jazayeri, B., Reacxion)
Commercializing a new chemical process can be as simple as installing one or more homogenous batch reactor(s), or as complex as designing a fully integrated chemical complex requiring one or more heterogeneous reaction steps processing gas, liquid and/or solids, with other units required to prepare feeds, recover products/byproducts and recycle streams.